Managed File Transfer

 View Only

Performing a Thread Dump in Windows Using the IBM JDK

By Tanvi Kakodkar posted Tue January 21, 2020 06:50 AM

  
Originally updated on November 23, 2016 by RyanWood_IBM

For Windows IBM JDK, there are two options, one to start SI in console mode (start_si_console.cmd) and execute CTRL+BREAK or following the instructions below using psexec and sendsingal.exe
 
Recommendation for thread dumps on Windows is using the psExec and SendSignal.exe (or jstack for Oracle JDK), as using the console mode is not practical for most Production environments.
 
Please Note there are 2 Windows JDK for IBM (32 bit and 64bit) while the process is the same, there is a 64 bit and a 32 bit version of the sendsignal.exe. Please use appropriately.

 

Procedure:

1) Download psexec.exe* directly on the server

 

2) Download 64bit "SendSignal.exe" 3rd party program here 
 
3 ) Launch the Remote Desktop Client (mstsc.exe) with the /admin switch
 
Use PsExec.exe to execute SendSignal.exe
 
Example Usage
PsExec.exe -s "C:\SendSignal.exe" 5000
SendSignal requires the Java Process ID. To determine the Java PID:
 
Right-click an empty area on the task bar and select Task Manager.
Select the Processes tab.
If you are not the same user who owns the JVM process, check Show processes from all users at the bottom of Task  Manager.
Select View > Select columns... from the menu bar.
Check PID (Process Identifier).
Click the OK button.
Click on the Image Name column to resort the processes by name.
Locate the process named "noapp.exe"
Note of the number in the PID column.
 
4) The resulting javacore file will be placed in the <si-install> root directory

 

Another option , that works on the IBM/Oracle JDK for Windows

If you only need thread dumps once a minute or less for Windows instances, then you can just add an empty file named threadDumpTrigger.txt in the install directory.

In the SI install directory,  create an empty file named threadDumpTrigger.txt, it is case sensitive.  it will disappear within a minute or two,  when it disappears the thread dump is complete.  It will go to noapp log with the date/time stamp.  It checks every 60 seconds for the file so you can only do it that quickly.  It is not as comprehensive as generating a javacore however.


#IBMSterlingB2BIntegratorandIBMSterlingFileGatewayDevelopers
#DataExchange
0 comments
25 views

Permalink