All Apps and Add-ons

Monitoring of Java Virtual Machines with JMX stopped working after CPU spike

amotta
New Member

Hi,

I started working with Splunk a couple of months ago, and we are currently using Monitoring of Java Virtual Machines with the JMX app to monitor the health of JVM. Lately, I noted an issue where the app stopped working and getting data from JVM after the server CPU spiked to 100%. I tried to restart Splunk on the server and checking logs; I have the following error:

2023-07-04 08:18:46 ERROR Logger=jmx://XXXXX host=XXXXX, jmxServiceURL=, jmxport=XXX, jvmDescription=XXXX, processID=0,stanza=jmx://XXXXX,systemErrorMessage="Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
java.io.EOFException]"

It was working before the CPU issue, and the server had no changes. I double-checked all configurations, and tried restarting Splunk and reinstalling the app, but it always returned the same error. Does anyone have a clue?

Labels (1)
0 Karma
Get Updates on the Splunk Community!

Modern way of developing distributed application using OTel

Recently, I had the opportunity to work on a complex microservice using Spring boot and Quarkus to develop a ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had 3 releases of new security content via the Enterprise Security ...

Archived Metrics Now Available for APAC and EMEA realms

We’re excited to announce the launch of Archived Metrics in Splunk Infrastructure Monitoring for our customers ...