Custom Handler logging not working in Jboss Wildfly 10.x

Description

Hi

when applying the agent to Jboss Wildfly 10.1, a custom-handler defined logger stops working. Jboss is not starting up.

Following parameter were added for JVM to workaround https://inspectit-performance.atlassian.net/wiki/spaces/DOC18/pages/93009239/WildFly+8.x.x+-+10.x.x

1 -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager,rocks.inspectit.agent.java -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:/opt/jboss10/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.4.Final.jar -javaagent:/opt/inspectit/inspectit-agent.jar -Dinspectit.repository=185.2.140.2:9070 -Dinspectit.agent.name=top_cav_test_vm-cos-int4

following output on startup

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 java.lang.IllegalArgumentException: Failed to load module "biz.paluch.logging" for handler "Logstash" at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:64) at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:51) at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:142) at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:673) at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:583) at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:521) at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97) at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:514) at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:476) at java.util.logging.LogManager$3.run(LogManager.java:399) at java.util.logging.LogManager$3.run(LogManager.java:396) at java.security.AccessController.doPrivileged(Native Method) at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396) at java.util.logging.LogManager.access$800(LogManager.java:145) at java.util.logging.LogManager$2.run(LogManager.java:345) at java.security.AccessController.doPrivileged(Native Method) at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338) at java.util.logging.LogManager.getLogManager(LogManager.java:378) at java.util.logging.Logger.demandLogger(Logger.java:448) at java.util.logging.Logger.getLogger(Logger.java:502) at rocks.inspectit.agent.java.javaagent.JavaAgent.<clinit>(JavaAgent.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:386) at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:401) Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoader at org.jboss.logmanager.config.AbstractPropertyConfiguration$ModuleFinder.getClassLoader(AbstractPropertyConfiguration.java:463) at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:62) ... 26 more

This is also referring to https://inspectit-performance.atlassian.net/browse/INSPECTIT-2255, but that ticket was for Jboss6

thx

EDIT (cannot add comments)

I have adjusted the parameters to this

1 -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:/opt/jboss10/jboss-modules.jar -Xbootclasspath/p:/opt/jboss10/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.4.Final.jar -javaagent:/opt/inspectit/inspectit-agent.jar -Dinspectit.repository=185.2.140.2:9070 -Dinspectit.agent.name=top_cav_test_vm-cos-int4

But sadly the same result. Like said, the question is hereby, if a workaround for a Jboss 6 is still working for a Jboss10....

Environment

Jboss WIldfly 10.1.0, Linux CoreOS 7.3, Java V1.8.0_131

Status

Assignee

Unassigned

Reporter

Dejan Bromm

Labels

Pull Request

None

Integrator

None

Components

Sprint

Affects versions

1.8.5

Priority

Medium
Configure