Splunk AppDynamics

Issue in executing java agent on JBoss

CommunityUser
Splunk Employee
Splunk Employee

Getting this issue after giving java agent path on the jvm and when restarting the jvm giving this error in server log and jvm is not starting.

13:47:24,861 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1
13:47:26,228 INFO  [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
13:47:26,417 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting
13:47:28,808 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.NoClassDefFoundError: com/singularity/ee/agent/appagent/entrypoint/bciengine/FastMethodInterceptorDelegatorBoot
        at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java)
        at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) [rt.jar:1.7.0_79]
        at org.jgroups.conf.ClassConfigurator.parse(ClassConfigurator.java:253)
        at org.jgroups.conf.ClassConfigurator.readMappings(ClassConfigurator.java:246)
        at org.jgroups.conf.ClassConfigurator.init(ClassConfigurator.java:88)
        at org.jgroups.conf.ClassConfigurator.<clinit>(ClassConfigurator.java:61)
        at org.jgroups.stack.Protocol.<init>(Protocol.java:58)
        at org.jgroups.protocols.TP.<init>(TP.java:586)
        at org.jgroups.protocols.UDP.<init>(UDP.java:42)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_79]
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_79]
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_79]
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_79]
        at java.lang.Class.newInstance(Class.java:379) [rt.jar:1.7.0_79]
        at org.jboss.as.clustering.jgroups.subsystem.JGroupsSubsystemXMLReader_1_1.parseTransport(JGroupsSubsystemXMLReader_1_1.java:157)
        at org.jboss.as.clustering.jgroups.subsystem.JGroupsSubsystemXMLReader_1_1.parseStack(JGroupsSubsystemXMLReader_1_1.java:129)
        at org.jboss.as.clustering.jgroups.subsystem.JGroupsSubsystemXMLReader_1_1.readElement(JGroupsSubsystemXMLReader_1_1.java:85)
        at org.jboss.as.clustering.jgroups.subsystem.JGroupsSubsystemXMLReader_1_1.readElement(JGroupsSubsystemXMLReader_1_1.java:47)
        at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
        at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
        at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1035) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
        at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:469) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
        at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
        at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
        at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
        at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
        at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133)
        at org.jboss.as.server.ServerService.boot(ServerService.java:321) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
        at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:254)
        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
Caused by: java.lang.ClassNotFoundException: com.singularity.ee.agent.appagent.entrypoint.bciengine.FastMethodInterceptorDelegatorBoot from [Module "org.apache.xerces:main" from local module loader @4098d3f6 (finder: local module finder @7183dc9b (roots: /jboss/EAP-6.3.0/jboss-eap-6.3/modules,/jboss/EAP-6.3.0/jboss-eap-6.3/modules/system/layers/base))]
        at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final-redhat-1]
        at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final-redhat-1]
        at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final-redhat-1]
        at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final-redhat-1]
        at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final-redhat-1]
        ... 30 more

13:47:28,835 INFO  [org.jboss.as] (MSC service thread 1-13) JBAS015950: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) stopped in 25ms

Labels (1)
0 Karma

Mohammed_Rayan
Contributor

Apmosys,

Verify your JVM startup options as given in the below link and see if you have added the below startup settings.

https://docs.appdynamics.com/display/PRO42/JBoss+and+Wildfly+Startup+Settings

Linux

In Linux, you can populate the path dynamically with the following code: 

JBOSS_MODULES_SYSTEM_PKGS ="org.jboss.byteman,com.singularity,org.jboss.logmanager"

JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager"
JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:$(ls ${JBOSS_HOME}/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-*.jar)"

If using the ${JBOSS_HOME} variable, as in the example, be sure to set the variable to the directory to the JBoss installation directory on your system. 

The path to the LogManager JAR file under the JBoss home can vary by JBoss version. Be sure to check your system and adjust the path as shown in the example accordingly. 

Regards,

Mohammed Rayan

0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...