DX Application Performance Management

Expand all | Collapse all

10.5.1.8 and 10.5.2 SP2 Agent Issue solved installing 10.7.0.45 Agent

  • 1.  10.5.1.8 and 10.5.2 SP2 Agent Issue solved installing 10.7.0.45 Agent

    Posted 03-08-2018 10:45 AM

    Hi all,

    we had a problem with agent for WAS vers.10.5.1.8 and 10.5.2 SP2:

    WAS Version : 8.5.5.11

    Java: 1.7.0_121 (64 bit)

     

    Problem description:

    - negative values on MD EJB Concurrent Invocations

    - presence of a directory in Investigator tree, under the was node, with "null" label

    - log errors: 

    3/08/18 03:22:19 PM CET [ERROR] [IntroscopeAgent.Agent] An error occurred formatting jms client metric namenull

    3/08/18 03:22:19 PM CET [ERROR] [IntroscopeAgent.Agent] Exception starting method tracer com.wily.introscope.agent.trace.frontend.jms.JMSFrontendTracer actual trace for com.sun.proxy.$Proxy40.onMessage

     

    Problem resolution:

    We can confirm that the issue has been solved with 10.7.0.45 version of WAS Agent.



  • 2.  Re: 10.5.1.8 and 10.5.2 SP2 Agent Issue solved installing 10.7.0.45 Agent

    Posted 05-04-2018 10:30 AM

    I am also having this issue with 10.5.2 Agents.

    Short of disabling JMS tracing, is there a work-around in the interim while waiting to upgrade to 10.7?



  • 3.  Re: 10.5.1.8 and 10.5.2 SP2 Agent Issue solved installing 10.7.0.45 Agent

    Posted 05-04-2018 11:24 AM

    You'll likely need to skip these proxy classes, but without seeing the AutoProbe and a debug log, I can't tell for sure.

    I would suggest opening a ticket on this one.



  • 4.  Re: 10.5.1.8 and 10.5.2 SP2 Agent Issue solved installing 10.7.0.45 Agent

    Posted 05-14-2018 10:57 AM

    I am having similar issue w/ "null" metrics for webMethods Integration Server 9.5 agent w/ APM Introscope Agent v10.5.2 SP2