Tracing Active Threads in JAM Console reports error -128 JVM 0 is not active
(Doc ID 555142.1)
Last updated on FEBRUARY 18, 2025
Applies to:
Enterprise Manager Base Platform - Version 10.2.0.4 to 10.2.0.4 [Release 10.2]Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
After installing the JAM console and deploying JAM agent successfully,
you decide to trace active threads for the monitored JVM.
In JAM console,
1. click on Java tab
2. select the active JVM
3. click on Trace Active Threads sub tab
After some time you see message on screen:
-128 JVM 0 is not active
Checking the logs in ../JAMSERV/logs/error.log shows error messages below:
JAM Console: Socket timed out after recv -- client <ip>:<port> is not Active
JAM CONSOLE: JVM 0 is not active
JAM Cons Err Processing Request: 128 JVM 0 is not active
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |