How do I perform a thread dump on my system to give me further insight into what GoAnywhere MFT is doing during a specific timeframe? Answer:
Thread dumps can be a great way to troubleshoot performance issues within MFT, including jobs stuck in an active state, active sessions, or stability issues that suddenly have crept up out of nowhere. Nearly all of the examples I just listed are occasionally observed and have a number of differing causes. A thread dump can help in analyzing where the threads the application is using are being allocated. Before conducting dumps on any system, be sure to check your system has adequate disk space so your dump does not get truncated. It is recommended to create multiple thread dumps to be sure to catch the issue at hand. Windows:
You first need to gather the process ID of your GoAnywhere instance. In order to do this, you must be on the server hosting the GoAnywhere instance.
Open Task Manager and navigate to the "Details" tab. Under name, search for "tomcat.exe". If your system has multiple instances of tomcat.exe, right click on the instance and click Properties. Under the "General" tab, look at the "Location" field. This should show the location of your GoAnywhere MFT instance on the filesystem. If this shows a different location, get out of the Properties dialog box, and repeat the process until you find the correct instance.
Once you find the correct tomcat.exe instance, navigate out of the Properties dialog box. Again, right click on the instance, and click "Create dump file." This will generate a dump and show you the location of the dump saved in the filesystem. IBM i:
IBM I utilizes the WRKJVMJOB command to generate thread dumps.
• Type in the WRKJVMJOB command. This will return a list of all the JVMs on the system.
• Find the JVM you are wanting to perform the dump on and press 5 (work with) and then enter to select the appropriate JVM.
• Select 32 (Java dump). This make take a minute.
• Select option 9 (Display Job Log). Here you can find the location of the dump within the file system.
From here you open the dump and analyze it to locate possible issues. Linux/Unix:
Linux also offers a couple options for obtaining thread dumps.
Kill -3 [pid of tomcat]
Without redirection, this will print the dump to catalina.out. A very large catalina.out file can cause problems with the dump. Redirect the output of the command to another file to combat this issue.
For additional information on thread dumps, please view the referenced sources below: https://stackoverflow.com/questions/185 ... hread-dump http://www-01.ibm.com/support/docview.w ... s8N1012559 https://helpx.adobe.com/experience-mana ... dDump.html https://dzone.com/articles/how-analyze- ... read-dumps