After upgrade of APM Java agent to 10.5 the JMS node has become greyed out and no metrics are visible.

Document ID:  TEC1659648
Last Modified Date:  07/17/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Application Performance Management

Releases

  • CA Application Performance Management:Release:10.3
  • CA Application Performance Management:Release:10.5
  • CA Application Performance Management:Release:10.5.1
  • CA Application Performance Management:Release:10.5.2
  • CA Application Performance Management:Release:CA APM as a Service 1.2

Components

  • APM AGENTS:APMAGT
Symptoms:

After upgrade of APM Java agent to 10.5 the JMS node has become greyed out and no metrics are visible.

Environment:
APM Java agent 10.3 and later release.
Cause:

Since APM 10.3 Java agent the JMS Node is no longer used to display JMS metrics. 

Resolution:

In the APM 10.3 Java agent the JMS support was enhanced to include correlation and at the same time the JMS metrics were moved to be under the Frontends & Backends nodes.

Additional Information:

The 10.3 Release Notes has more details of this change:

APM 10.3 Release Notes > Java Agent > JMS 1.1 Support

Java Agent 

JMS 1.1 Support 

A new set of agent tracers extends the correlation visibility to include JMS 1.1 applications. Metrics are gathered under Frontends|Messaging Services and Backends|Messaging Services, and these metrics appear as component data within a transaction trace.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >