Details

    • Type: Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      There are many issues which will cause an exception with the message:

      ""The LogManager was not properly installed""

      This is due to the fact that jboss assumes that it is the first to initialize/load java.util.logging.LogManager.
      In case the java LogManager is loaded within a different classloader than the one which is expected by jboss, the server will not start and will log the above error message. Whereas most classes will load the log manager within the system classloader, jboss is loading it within another classloader.

      Therefore setting -Djava.util.logging.manager=org.jboss.logmanager.LogManager does not help.

      This is the case when starting the server with -Dcom.sun.management.jmxremote.
      This is also the case when using a wrapper (sourceforge.net/projects/yajsw)
      or any other java class, wrapper or agent.

      The best solution will be to avoid using java.util.logging as its implementation is causing more harm than good and switch to some internal logging api.

      – Ron

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jamezp James Perkins
                Reporter:
                rzo12345 ron zo
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: