Troubleshooting Performance and Connection Issues in Informatica: How to Collect Jstack on Developer Tool

🔍 Understanding what is Jstack and its purpose.

⏱️ Knowing when to collect Jstack on the developer tool.

🎥 A quick demonstration of how to collect Jstack on the developer tool.

🔍 To collect Jstack on Developer Tool, you need to find the process ID of the tool by going to the task manager and looking for the process name java w dot exe.

💻 In the newer releases of the informatica client, the process name appears as the application name 'has own platform and 410'. In prior releases, it appears as 'Java TM platform SC binary'. To avoid confusion, look for the process name Java EE dot exe.

🔢 If you have multiple clients running, you can verify the path from which the Java W is executed or invoked by using the command line.

🔍 To collect a Jstack, navigate to the Java bin location and execute Jstack CMD.

📁 Redirect the Jstack output to a file for better analysis.

⚠️ Collecting multiple Jstacks is recommended for troubleshooting performance issues.

🔍 Collecting Jstack at regular intervals helps determine if a thread is progressing or stuck.

💡 It is recommended to collect at least three Jstacks on the developer client.

📚 Additional information can be found in the Oracle documentation or the informatica knowledgebase.