Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] - Since 2.0.0 Wildfy Server refuses to start #1465

Closed
ClaudioWaldvogel opened this issue Jun 9, 2022 · 0 comments
Closed

[Feature] - Since 2.0.0 Wildfy Server refuses to start #1465

ClaudioWaldvogel opened this issue Jun 9, 2022 · 0 comments
Labels
area/documentation idea A rough idea for a feature or extension

Comments

@ClaudioWaldvogel
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Since version 2.0.0 Ocelot Agent prevents Wildfly servers from starting. rocks.inspectit.ocelot.agent.AgentMain initializes the logging system - but Wildfly is very stubborn at this point and expects org.jboss.logmanager.LogManager as LogManager.
This is a common problem when using Java agents with Wildfly.

Caused by: java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:195) at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:131) at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:103) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:144) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:508)

Describe the solution you'd like
Update documentation how to configure Wildfly properly.

Java 8

-Djava.util.logging.manager=org.jboss.logmanager.LogManager
-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager  
-Xbootclasspath/p:<WILDFLY_HOME>/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-<version>.jar  
-Xbootclasspath/p::<WILDFLY_HOME>/modules/system/layers/base/org/wildfly/common/main/wildfly-common-<version>.jar
-javaagent:inspectit-ocelot-agent.jar

Java 11

-Dsun.util.logging.disableCallerCheck=true
-Djava.util.logging.manager=org.jboss.logmanager.LogManager
-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager
-Xbootclasspath/p:<WILDFLY_HOME>/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-<version>.jar
-Xbootclasspath/p::<WILDFLY_HOME>/modules/system/layers/base/org/wildfly/common/main/wildfly-common-<version>.jar
-javaagent:inspectit-ocelot-agent.jar
@ClaudioWaldvogel ClaudioWaldvogel added area/documentation idea A rough idea for a feature or extension labels Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation idea A rough idea for a feature or extension
Projects
None yet
Development

No branches or pull requests

1 participant