FAQs

Frequently Asked Questions - logmanager

FAQs - logmanager

Exception stack trace:

java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
        at org.jboss.logmanager.Logger.getLogger(Logger.java:61)
        at org.jboss.as.server.Main.main(Main.java:84)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.jboss.modules.Module.run(Module.java:312)

This exception is caused by a known bug in JDK that is documented here:

https://access.redhat.com/solutions/3234671

https://access.redhat.com/solutions/3370101

To prevent the exception, please add the following JVM system property to the JBoss startup script:

Windows (standalone.conf.bat or domain.conf.bat)

set "JAVA_OPTS=%JAVA_OPTS% -Dsun.util.logging.disableCallerCheck=true"

Unix/Linux (standalone.conf or domain.conf)

JAVA_OPTS="${JAVA_OPTS} -Dsun.util.logging.disableCallerCheck=true"