DX Application Performance Management

  • 1.  java.lang.NoClassDefFoundError: com/wily/introscope/agent/AgentShim

    Posted Aug 14, 2012 03:44 PM
    Hi All, we are trying to monitor Edifecs XeServer 7.0.8 and we are seeing following messages in xes.route.events.log ( agent comes up and reports well ) but xes.route.events.log keep growing with the following messages.


    Any Suggestions / Tips to resolve the same pls.


    bash-3.00#
    bash-3.00#
    bash-3.00# tail -20f xes.route.events.log
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSHelperBase.receiveMessage(JMSHelperBase.java:105)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSMessageReceiver.receiveMessage(JMSMessageReceiver.java:116)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSMessageReceiver.access$100(JMSMessageReceiver.java:15)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSMessageReceiver$MessageDeliveryThread.run(JMSMessageReceiver.java:202)[133:xes-endpoint-jms:7.0.8]
    2012-08-14 15:33:26.005 | SYNC | 00034 | ERROR | 271_Route[1] | Data Processor | Route component internal error | jms271 | jms:jms271 | {}
    java.lang.NoClassDefFoundError: com/wily/introscope/agent/AgentShim
    at com.stc.jms.client.STCMessageConsumer.receive(STCMessageConsumer.java)
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSHelperBase.receiveMessageInternal(JMSHelperBase.java:127)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSHelperBase.receiveMessage(JMSHelperBase.java:105)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSMessageReceiver.receiveMessage(JMSMessageReceiver.java:116)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSMessageReceiver.access$100(JMSMessageReceiver.java:15)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSMessageReceiver$MessageDeliveryThread.run(JMSMessageReceiver.java:202)[133:xes-endpoint-jms:7.0.8]
    2012-08-14 15:33:26.028 | SYNC | 00034 | ERROR | 271_Route[3] | Data Processor | Route component internal error | jms271 | jms:jms271 | {}
    java.lang.NoClassDefFoundError: com/wily/introscope/agent/AgentShim
    at com.stc.jms.client.STCMessageConsumer.receive(STCMessageConsumer.java)
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSHelperBase.receiveMessageInternal(JMSHelperBase.java:127)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSHelperBase.receiveMessage(JMSHelperBase.java:105)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSMessageReceiver.receiveMessage(JMSMessageReceiver.java:116)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSMessageReceiver.access$100(JMSMessageReceiver.java:15)[133:xes-endpoint-jms:7.0.8]
    at com.edifecs.etools.xeserver.component.endpoint.jms.JMSMessageReceiver$MessageDeliveryThread.run(JMSMessageReceiver.java:202)[133:xes-endpoint-jms:7.0.8]





    Thanking You,
    With Warm Regards - Jai.


  • 2.  RE: java.lang.NoClassDefFoundError: com/wily/introscope/agent/AgentShim

    Posted Aug 14, 2012 04:49 PM
    Jai,

    [font=Courier New]com.wily.introscope.agent.AgentShim[font] is a class in the [font=Courier New]Agent.jar[font]; it's very odd that a successfully instrumented JVM would not be able to find this class. I'm completely unfamiliar with [font=Courier New]Edifecs XeServer[font] and its structure, but is it possible that what you're seeing is being generated by a subprocess that is invoked by your instrumented application (Edifecs XeServer) but that isn't getting assigned the [font=Courier New]-javaagent[font] startup argument? If so, there may be some configuration option in the application that you can pursue to add the instrumentation to its child processes.


  • 3.  RE: java.lang.NoClassDefFoundError: com/wily/introscope/agent/AgentShim

    Posted Aug 14, 2012 10:33 PM
    Hi
    we used to get AgentShim not found exception when we deployed 911 in jboss7. the workaround for jboss was adding “-Djboss.modules.system.pkgs=com.wily,com.wily.*” in JAVA_OPT of standlone.sh ( along with -javaagent switch ). I am thinking you will probably have to let the app know abt com.wily packages somehow.