Agent cannot start if custom Logging Module is used in JBoss

Description

With JBoss 6.4.11 we have the problem that the JBoss cannot start with the agent, if a custom Logging Module is used in JBoss.

Assuming the following logging configuration in JBoss standalone.xml:

The following Java Options are used for the agent:

JavaOpts

-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager
-Djava.util.logging.manager=org.jboss.logmanager.LogManager
-Xbootclasspath/p:C:/daten/jboss/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.5.4.Final-redhat-1.jar
-Xbootclasspath/p:C:/daten/jboss/agent/inspectit-agent.jar
-javaagent:C:/daten/jboss/agent/inspectit-agent.jar
-Dinspectit.repository=localhost:9070
-Dinspectit.agent.name=MyAgent

When starting the JBoss with the agent, the following exception occurs and JBoss terminates:

If I remove the following JavaOptions (the ones that are striked through): ...

JavaOpts

-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager
-Djava.util.logging.manager=org.jboss.logmanager.LogManager
-Xbootclasspath/p:C:/daten/jboss/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.5.4.Final-redhat-1.jar
-Xbootclasspath/p:C:/daten/jboss/agent/inspectit-agent.jar
-javaagent:C:/daten/jboss/agent/inspectit-agent.jar
-Dinspectit.repository=localhost:9070
-Dinspectit.agent.name=MyAgent

... then, during start of JBoss, I get the following Error:

Environment

JBoss 6.4.11

Activity

Show:
Alexander Wert
November 15, 2016, 7:00 AM
Ivan Senic
November 15, 2016, 8:08 AM

Seams they solve it with turning the logging off. Not sure what that means, but it must be possible then to overcome this one.

Ivan Senic
November 16, 2016, 2:29 PM

Alex it is not clear to us why did you not include to the boot class-path also the two other jars that we suggest in the documentation? This is also written in this CA page:

Can you try with this please? I have a 6.1.0 version of JBoss locally and it only works if this is set. The only difference here can be this custom logging module, but we doubt it. If it happens again, then maybe we need have this module and test it if needed. Can you please check and report back?

Ivan Senic
November 17, 2016, 1:51 PM

As problem is solved, can you add a short description here of what you did and close this ticket then. Thanks..

Alexander Wert
November 17, 2016, 2:22 PM
Edited

To solve this issue, use the following configuration:

-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager
-Djava.util.logging.manager=org.jboss.logmanager.LogManager
-Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.5.4.Final-redhat-1.jar
-Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.1.Final-redhat-1.jar
-Dmodule.path=$JBOSS_HOME/modules
-Xbootclasspath/p:$JBOSS_HOME/jboss-modules.jar
-javaagent:$AGENT_HOME/inspectit-agent.jar
-Dinspectit.repository=localhost:9070
-Dinspectit.agent.name=MyAgent

Assignee

Unassigned

Reporter

Alexander Wert

Labels

Integrator

None

Affects versions

Priority

Highest
Configure