Splunk Dev

OutOfMemoryError: Java heap space error in Splunk add-on for JMX

kkarthik_splunk
Splunk Employee
Splunk Employee

I am trying to reproduce a case where the following error occurs in splunkd.log and as a result data collection stops:

09-24-2019 21:44:45.713 +0200 ERROR ExecProcessor - message from "python /$SPLUNK_HOME/etc/apps/Splunk_TA_jmx/bin/jmx.py" Exception in thread "Thread-20" java.lang.OutOfMemoryError: Java heap space

In this case, the datacollection resumes only after restarting Splunk.

I am able to get OutOfMemory Error by reducing the maximum heap space in java by making the following changes in file

$SPLUNK_HOME/etc/apps/Splunk_TA_jmx/bin/java_consts.py (line 43) 
JAVA_COMMON_ARGS = [JAVA_EXECUTABLE, "-Xmx8m","-classpath", CLASSPATH, "-Dconfighome=" + CONFIG_HOME,
                    "-Dsplunkhome=" + SPLUNK_HOME]

However, in my case, the OutOfMemory Error goes away after a few minutes and datacollection resumes.

For the issue I am trying to reproduce, 151 inputs are configured in the addon.

Can anyone tell why this error occurs, how can I reproduce it and is there a way to resolve it?

Labels (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...

Splunk Agent Observability: Measuring AI Value with Splunk Tokenomics on AWS

The AI landscape is moving faster than ever, and our latest 2026 State of Observability report provides the ...

Enterprise Security Watch Party: What’s New in 8.8 - Recap

Splunk Community HQ hosted a Splunk Enterprise Security Watch Party: What’s New In ES 8.8 last Thursday. I had ...