All Apps and Add-ons

AMQP data input monitor stops streaming messages after hitting error: " java.lang.OutOfMemoryError: GC overhead limit exceeded"

malavika
Engager

I have configured amqp modular data input to consume data from a rabbitmq queue. I have increased my heap maximum from 64M upto 1024M and still tend to hit the heap issue. After which the streaming to splunk stops until the data input monitor is disabled and then re-enabled.

Are we hitting a memory leak issue? Is there a way I can ensure I continue streaming in the data without hitting the heap issue.

ERROR ExecProcessor - message from "python /local/mnt/splunk/etc/apps/amqp_ta/bin/amqp.py" Exception in thread "Thread-3" java.lang.OutOfMemoryError: GC overhead limit exceeded

Damien_Dallimor
Ultra Champion

You also emailed me , so copy/pasting that reply here :

Excessive memory use is not the same as a Memory Leak.

Allocate more memory.

As per the docs :

alt text

yAlff
Path Finder

Hello Damien,
can you please check the picture? I cannot see it and also need a resolution for this.

0 Karma
Get Updates on the Splunk Community!

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...