ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Windows .net APMAgent Thread IDs do not match Windows thread ID

book

Article ID: 187682

calendar_today

Updated On:

Products

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

Issue/Introduction

The thread Id that are generated in .NET agent from the APM Investigator do not match up to any thread ids in Windows.
So, we arenot able to match the thread id to Windows thread to identify the thread when selecting the thread dump in the APM Investigator GUI.

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/using/apm-webview/locate-application-problems.html

See (Optional) Collect and Analyze Thread Dumps

You can examine a thread dump using several ways as described in the above link

Even you can open these saved text thread dumps using few publicly available third-party thread dump analyzers.

Environment

All supported releases.

Resolution

APM is not capturing all Windows threads. Note that APM is not providing native threads by design, Our format  is different for thread ids. While comparing two or three thread dumps from different sources,  we recommend analyzing thread dumps per the document in the above link or at least using third- party analyzers. For example, you could use fast thread analyzer to analyze our thread dumps which gives in-depth analysis.(See https://fastthread.io/)