After adding the OverOps agent JBoss fails to start with
Failed to load the specific log manager class org.jboss.logmanager.LogManager
or a similar Error message.
Java 11 and newer JBoss/Wildfly Agent: any version
Ensure that (the sequence is important):
com.sparktale.bugtaleis added to
-Djboss.modules.system.pgksargument (see example below)
- OverOps is configured after the above
Starting with JBoss EAP 7.4; you can use
MODULE_OPTSto attach the OverOps agent which will ensure the correct sequence.
-Xbootclasspath/aflag if still used
Starting with jdk11, having JBoss logmanager on the boot classpath causes various problems, where the main one could be seen in: https://issues.redhat.com/browse/MODULES-393.
As seen in the link above Redhat changed how they work and now instead of supplying the logmanager, through
-Xbootclasspath/a flag they supply their own java agent which loads the modules for himself and other agents as well.
These need to be configured correctly to work side by side with other agents.