ClassNotFoundException after enabling a Java Agent on JBoss EAP 6.x

Solution Verified - Updated -

Issue

  • A ClassNotFoundException occurs during start up of JBoss EAP 6.x in standalone mode after enabling a Java Agent (specifically the Introscope Agent). The standalone.conf was updated to include the Introscope Agent:
# enable Introscope agent
WILY_OPTIONS="-javaagent:/hosting/products/introscope/Agent.jar -Dcom.wily.introscope.agentProfile=/hosting/products/introscope/core/config/bofa/R3.profile -Dcom.wily.introscope.agent.agentName=r3-sit1-01"
JAVA_OPTS="${WILY_OPTIONS} ${JAVA_OPTS}"

The instance couldn't be started. Here is the error from the server.log:

Exception in thread "main" java.lang.NoClassDefFoundError: com/wily/introscope/agent/probe/io/ManagedFileInputStream
        at java.lang.Class.getDeclaredConstructors0(Native Method)
...
Caused by: java.lang.ClassNotFoundException: com.wily.introscope.agent.probe.io.
ManagedFileInputStream from [Module "org.codehaus.woodstox:main" from local modu
le loader @3fd03371 (roots: /var/lib/jboss-eap-6.0/modules)]
        at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:
190)
...

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.