Why does APM report a different value for Active Threads compared to jvisualvm?

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)
• INTROSCOPE

Issue/Introduction

Description:

In the jvisualvm the number of live/active threads always shows as a much higher value than is reported in the Investigator - as you can see from the screen shots below.

jvisualvm is reporting 69-72 threads:

<Please see attached file for image>

where as the APM Investigator is showing 40:

<Please see attached file for image>

Solution:

The thread count in APM does not include the agent and system threads, thus the APM thread count will always be lower than that reported by jconsole / jvisualvm.

Environment

Release:
Component: APMAGT