Return
-
Title
How to troubleshoot Java PSM Session Issues -
Description
When troubleshooting PSM Sessions that fail to connect (or report an error during the connection), what steps can be used to troubleshoot the root cause (for Java)? -
Resolution
Enabling the Java Console logs should help provide details on the activities of the TPAM Java Application.
To enable the logging, perform the following steps:
1. Open the Control Panel of the local workstation2. Click on the “Java” Application3. Click the “Advanced” tab4. Enable the checkbox for “Enable Tracing” and “Enable Logging” under the “Debugging” section5. Click “Ok”6. Delete all old logs from the Java folder:a. On Linux, Unix: “<user.home>/.java/deployment/log”b. On Mac OS X: “~/Library/Application Support/Oracle/Java/Deployment/log”c. On Windows: “<User Application Data Folder>\Sun\Java\Deployment\log”(Typically %userprofile%\AppData\LocalLow\Sun\Java\Deployment\log)
7. Replicate the error when connecting to the PSM session8. Gather the logs generated above
Also, the Java “Network Settings” should be gathered:
1. Open the Control Panel of the local workstation2. Click on the “Java” Application3. Click on the “Network Settings” button4. Document the setting selected
Additionally, a Network capture can be gathered from the Client Workstation:
1. On the workstation getting the error, launch a Network Capture utility (for example WireShark)2. Start a capture on the interface that is used to connect to TPAM3. Replicate the error4. Document the following:a. The IP Address of the Client Workstationb. The IP Address of the TPAM Appliancec. The IP Address of the DPA(s) if any exist in TPAM