[wildfly-dev] how a -javaagent can use logging and not blow up WildFly

[John Mazzitelli]

> > "oh, you just do this magical step and it works around the problem."
>
> With recent builds setting system property org.wildfly.logging.skipLogManagerCheck=true
> should workaround your problem.

Ah.. That's a good one to know.

I need something for earlier WildFly and EAP builds, though. But I recently found this solves my problem (this worked for me on both EAP6 and EAP7.1):

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"

That seems to fix my problem.