I am trying to run a Java application deployed as a .war file on WildFly with the SkyWalking agent enabled for monitoring. However, when I start WildFly, it fails to boot with the following error:

java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be .jboss.logmanager.LogManager. The subsystem has not been initialized and cannot be used. To use JBoss Log Manager, you must add the system property "java.util.logging.manager" and set it to ".jboss.logmanager.LogManager"

This results in a fatal error preventing WildFly from starting:

FATAL: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. - Server configuration file in use: standalone.xml

My Setup: I have:

Java application packaged as a .war file and placed in:

$JBOSS_HOME/standalone/deployments/app.war

SkyWalking agent (packaged as a .jar) added to WildFly’s standalone.conf file like this:

JAVA_OPTS="$JAVA_OPTS -javaagent:/opt/skywalking-agent/skywalking-agent.jar"

WildFly 35.0.1.Final running in standalone mode.

What I Have Tried: Verified that the .war file is correctly placed in standalone/deployments/ and WildFly detects it.

Checked server.log and found that WildFly crashes due to the log manager issue.

Searched online and found that JBoss WildFly requires .jboss.logmanager.LogManager for logging, but it seems SkyWalking changes this behavior.

As Skywalking doesnt support WildFly how to modify or configure it so that it supports WildFly

Do I need to configure something in SkyWalking?

Should I modify the standalone.conf file further?

Additional Information:

OS: Ubuntu 22.04

Java Version: JDK 17

WildFly Version: 35.0.1.Final

SkyWalking Version: 9.2.0

I am trying to run a Java application deployed as a .war file on WildFly with the SkyWalking agent enabled for monitoring. However, when I start WildFly, it fails to boot with the following error:

java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be .jboss.logmanager.LogManager. The subsystem has not been initialized and cannot be used. To use JBoss Log Manager, you must add the system property "java.util.logging.manager" and set it to ".jboss.logmanager.LogManager"

This results in a fatal error preventing WildFly from starting:

FATAL: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. - Server configuration file in use: standalone.xml

My Setup: I have:

Java application packaged as a .war file and placed in:

$JBOSS_HOME/standalone/deployments/app.war

SkyWalking agent (packaged as a .jar) added to WildFly’s standalone.conf file like this:

JAVA_OPTS="$JAVA_OPTS -javaagent:/opt/skywalking-agent/skywalking-agent.jar"

WildFly 35.0.1.Final running in standalone mode.

What I Have Tried: Verified that the .war file is correctly placed in standalone/deployments/ and WildFly detects it.

Checked server.log and found that WildFly crashes due to the log manager issue.

Searched online and found that JBoss WildFly requires .jboss.logmanager.LogManager for logging, but it seems SkyWalking changes this behavior.

As Skywalking doesnt support WildFly how to modify or configure it so that it supports WildFly

Do I need to configure something in SkyWalking?

Should I modify the standalone.conf file further?

Additional Information:

OS: Ubuntu 22.04

Java Version: JDK 17

WildFly Version: 35.0.1.Final

SkyWalking Version: 9.2.0

• java
• jboss
• wildfly
• skywalking

1 Answer 1

Instead of using the JAVA_OPTS for the agent arguments, try using the MODULE_OPTS. That will allow the log manager to be configured before the agent attempts to log anything.