java.lang.RuntimeException: WFLYCTL0079: Failed initializing module org.jboss.as.logging
search cancel

java.lang.RuntimeException: WFLYCTL0079: Failed initializing module org.jboss.as.logging

book

Article ID: 431618

calendar_today

Updated On:

Products

DX SaaS DX Operational Observability DX Application Performance Management

Issue/Introduction

The application fails to start with the java agent, the below ERROR is reported in the Jboss app logs:

JBWS022052: Starting JBossWS 5.4.15.Final-redhat-00001 (Apache CXF 3.5.10.redhat-00001)
[10.496s][info][gc] GC(7) Pause Young (Normal) (G1 Evacuation Pause) 1289M->142M(25600M) 28.167ms

ERROR [org.jboss.as.controller.management-operation] (apm-jmx-client-pool-2:worker thread-1) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
("subsystem" => "jca"),
("workmanager" => "default")..

 org.jboss.as.controller.AbstractOperationContext executeStep
ERROR: WFLYCTL0013: Operation ("parallel-extension-add") failed - address: ([])
java.lang.RuntimeException: WFLYCTL0079: Failed initializing module org.jboss.as.logging
at [email protected]//org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:115)
at [email protected]//org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1063)
at [email protected]//org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:784)
at [email protected]//org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:470)

Environment

DX O2 25.11 and onwards

Cause

Accessing JMX beans before JBoss initializes the logger will cause this error, as the JMX mbean server internally will call the Logger.getLogger().
 
We have added a delay property to delay JMX service until application starts:
 
introscope.agent.remotejmx.delayInSeconds=...
 
Without delay we have essentially a race condition of remoteJMXService and JBoss initializing and if JBoss wins there is no issue, if JBoss loses there's this problem.

Resolution

1.Stop JVM
2.Open the <AGENT_HOME>/extensions/<jmx-boss folder>/jmx-jboss extension bundle.profile
3. Add at the end of the file:
introscope.agent.remotejmx.delayInSeconds=30
4. Save and restart the jvm

Additional Information

Techdocs DX Agents - Jboss configuration