Situation:
In some cases, Adeptia will encounter an issue that will require more information that is not available in the application logs. Generally, these issues will be related to process flows stuck in the running state or performance issues. When this occurs, the support team will need the thread and heap dumps from jstack and jmap
Install:
To setup jstack and jmap to gather the necessary heap and thread dump, you'll need to install a Java Development Kit (JDK). For the Adeptia v6.2 Release, the Java Runtime Environment is 1.7.60, so installing the corresponding JDK is advised
1) Download JDK 1.7.60 from the oracle website (Linux or Windows depending on your OS)
2) Install the JDK on the same machine and drive that Adeptia is installed on
3) Once installed, navigate to the bin directory of the JDK installation
Ex: C:\Program Files\Java\jdk1.7.x\bin
Identify Adeptia Processes:
Linux
1) Use the ps aux | grep adeptia command to pull up the running Adeptia processes
2) Identify the PID of the Kernel and Webrunner
Windows
1) Task Manager > Processes tab
2) Identify the PID of the Kernel and Webrunner
Thread dump:
1) Navigate to the the bin directory of the JDK installation
2) Run the following command for the Kernel. In this case the PID of the Kernel is 27250
jstack -F 27250 >> Kernelthread.out 2>&1
3) A Kernelthread.out file will be generated in the bin directory of the JDK installation
4) Repeat steps 2 and 3 for the Webrunner process
Heap dump:
1) Navigate to the the bin directory of the JDK installation
2) Run the following command for the Kernel. In this case the PID of the Kernel is 27250
jmap -F -dump:format=b,file=Kernelheap.hprof 27250
3) A Kernelheap.hprof file will be generated in the bin directory of the JDK installation
4) Repeat steps 2 and 3 for the Webrunner process
Comments
0 comments
Article is closed for comments.