Lionel Cons created APLO-257:
--------------------------------
Summary: Better memory usage (avoid Java OOM exceptions)
Key: APLO-257
URL: https://issues.apache.org/jira/browse/APLO-257
Project: ActiveMQ Apollo
Issue Type: Improvement
Environment: apollo-99-trunk-20120902.143447-110
Reporter: Lionel Cons
When running a stomp-benchmark based stress test against Apollo, it generated
several OOM exceptions like:
2012-09-03 23:51:45,275 | WARN | handle failed |
java.lang.OutOfMemoryError: Java heap space
2012-09-03 23:52:02,428 | WARN | |
java.lang.OutOfMemoryError: Java heap space
2012-09-03 23:52:01,372 | WARN | Error for /broker |
java.lang.OutOfMemoryError: Java heap space
2012-09-03 23:51:55,554 | WARN | Problem scavenging sessions |
java.lang.OutOfMemoryError: Java heap space
The JVM already had 8GB of heap. FWIW, here are the options used: "-server
-Xmx8192m -Xms4096m -XX:-UseBiasedLocking".
Would it be possible for Apollo to detect when its getting close to the JVM
limits and adjust its memory usage accordingly (reducing buffers, swapping
messages to disk...)?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
