[ https://issues.jboss.org/browse/ISPN-7599?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7599: ------------------------------------------- A snippet from WF mailing list: {quote} Inside standalone.conf: # Add "org.jboss.logmanager" to the JBoss Modules system packages if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman,org.jboss.logmanager" fi # Explicitly tell the VM to use the JBoss Log Manager via -Djava.util.logging.manager system property. # Use the -javaagent VM option to load the agent JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager -javaagent:my-agent.jar" This is the correct solution. Skipping the check could potentially be an issue if the log manager installed is not the jboss-logmanager. Adding system module (or adding the library to the boot class path) and the java.util.logging.manager as the first system property in the JAVA_OPTS is the correct way to handle this. {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)