How to analyze the thread dump with IBM Thread and Monitor Dump Analyzer.

Products	Versions
TIBCO ActiveMatrix BusinessWorks	-
Not Applicable	-

Description

Description:

The process of analyzing a thread dump is explained by using a sample thread dump. This thread dump was created when a JMS message expires. In this case, the engine was running from the command line to create a thread dump and the EMS client trace was enabled. Refer to KB 28813 to get the thread dump file. EMS client tracing can be enabled by executing the following command from the EMS admin console. Make sure that the engine trace (Trace.Task.*=true) is enabled.

set server client_trace=true

Refer to the attached (Filename: IBM Thread and Monitor Dump Analyzer for java .456.jar) file and open the tools. The tool can be downloaded from:

https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=2245aa39-fa5c-4475-b891-14c205f7333c

Open the thread file with this tool. In this sample, you will find the JMS message expires without reason. After enabling the EMS client trace, you will find the trace below in the attached BW logs (Filename:BWlogs.txt).

2015 Oct 16 11:06:03:649 GMT +2 BW.EAI_BusinessServices_JMS_7-EAI_BusinessServices_JMS_7-01-01 Info [BW-User] VOD-000-000 [ASPS00006-MOBILE-31620515499-16102015-104647102] [BS00207] Started JMSInterface for the Business Service. 2015-10-16 11:06:03.650 [29308680 Thread-71] [TIBCO EMS]: [J] Msg Expired conn=13455600 sess=1573792797 seqid=11269538087 msgid=ID:EMS2HR.529355DBAD635D06202F:22663

2015-10-16 11:06:03.650 [29308680 Thread-71] [TIBCO EMS]: [J] Msg Expired conn=13455600 sess=1573792797 seqid=11269542999 msgid=ID:EMS2HR.529355DBAD635D0719AA:22330

2015-10-16 11:06:03.650 [15179619 Thread-69] [TIBCO EMS]: [J] Msg Expired conn=13455600 sess=1573792770 seqid=11269528098 msgid=ID:EMS2HR.529355DBAD63525A5BFE:2138445

2015 Oct 16 11:06:03:650 GMT +2 BW.EAI_BusinessServices_JMS_7-EAI_BusinessServices_JMS_7-01-01 Info [BW-Core] BWENGINE-300007 Job-355518004: Process Started 2015-10-16 11:06:03.650 [15179619 Thread-69] [TIBCO EMS]: [J] Msg Expired conn=13455600 sess=1573792770 seqid=11269528856 msgid=ID:EMS2HR.529355DBAD63525A3B3B:2169521

You will see many threads (blue thread) in the "Waiting" status in the IBM tools. You will see these Waiting threads are also the Consumer thread. All of them are waiting for lock "73e46688". It is locked by "EngineReminderQueue".

Issue/Introduction

How to analyze the thread dump with IBM Thread and Monitor Dump Analyzer.

Resolution

The monitor lock 73e46688 was waiting on a JDBC operation. Refer to the attached (Filename: 2.png) file. After fixing the database, the issue will be resolved.

Additional attached references (Filename: 1.png and thread2.txt).

Additional Information

https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=2245aa39-fa5c-4475-b891-14c205f7333c

Attachments

How to analyze the thread dump with IBM Thread and Monitor Dump Analyzer. get_app

Welcome to "KB Articles"