Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 10.1.0.Final
    • Fix Version/s: 10.1.1.Final
    • Component/s: Server
    • Labels:
      None

      Description

      Currently the server uses JBoss LogManager, because that's what the WildFly server used.

      It works, but the properties-based configuration is kind of clunky: it uses almost the same format as java.util.logging, but there are differences. Also not many of our users are familiar with it: WildFly has its own logging configuration in the XML, and logging.properties is auto-generated.

      It would be better if we switched to log4j2 with a java.util.logging bridge.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                dan.berindei Dan Berindei
                Reporter:
                dan.berindei Dan Berindei
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: