JBoss Messaging (JMS) throws OutOfMemoryError with too many messages in queue
Issue
- Sometimes we reach 100000 messages in the queue and it causes a memory leak. How can I lower the maximum message numbers maintained in RAM?
- I been getting heap space memory error quite often. I have allocated the max available heap space to the JVM. For the queues/topics, the maxSize is -1, fullSize is 200000. For the 'busiest' queues/topics, messageCount can hit few 10k, or even few 100k. Message size varies as there are many different 'sources'
- We noticed some memory issues with our JBoss jms server (JBoss Messaging) during high loads. Since all messages of the queues are held in memory, this can be a problem if for some reason a consumer fails or is down for a while. If that happens we receive an OutOfMemory. This will keep on, with every restart, because all messages are loaded into memory again.
Is it possible to control this behaviour with some configuration parameters of the queue or the post office?
Environment
- JBoss Enterprise Application Platform (EAP)
- 5.x
- 4.3
- JBoss Messaging (JMS)
- JBoss-SOA-P 4.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.