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

Status

Assignee

Unassigned

Reporter

Alexander Wert

Labels

Pull Request

None

Integrator

None

Affects versions

Priority

Highest
Configure