Skip to Content

Background

There are occasions where Development resources will require a thread dump to debug a particular issue in SAP Sourcing. 

Prerequisites

To accomplish the procedure included here the user will need direct access to the Netweaver Console. The Screen shots here are with the standalone Windows Console SAPMMC. This also works with the web based console.

Procedure

1)      As a user with administrator access, Navigate to the AS Java Process Table open this selection.

2)      In the right hand pane pick the server instance you need a thread dump for.

Web Based Console.

/wp-content/uploads/2012/07/pic1_124561.png

SAPMMC — Windows

/wp-content/uploads/2012/07/pic2_124577.png

3)      Right mouse click on this selection and select Dump Stack (Web based Console)  Dump Stack Trace (SAPMMC version)

4)      Navigate to usr/sap/<SID>/J<NN>/work.

/wp-content/uploads/2012/07/pic3_124578.png

5)      Locate the std_server<N>.out file. Verify there are entries including thread information. Zip them up and send to SAP.

Typical Thread dump entry viewed in Wordpad…

“Daemon-0019: ODP_EVENT_CACHE_CHANGED (0)” cpu=327.60 [reset 327.60] ms allocated=3165248 B (3.02 MB) [reset 3165248 B (3.02 MB)] user=”” application=”sap.com/E-Sourcing-Server” prio=6 tid=0x000000002112b660 nid=0x3560 waiting on condition [0x000000003944f000..0x000000003944f8d0]

   java.lang.Thread.State: TIMED_WAITING (sleeping)

     at java.lang.Thread.sleep(J)V(Native Method)

     at com.sap.odp.comp.daemon.ResponsibleDaemonBase.waitForNewTriggers()V(ResponsibleDaemonBase.java:580)

     at com.sap.odp.comp.daemon.ResponsibleDaemonBase.run()V(ResponsibleDaemonBase.java:268)

     at java.lang.Thread.run()V(Thread.java:725)

   Locked ownable synchronizers:

     – None

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply