[APLO-257] Better memory usage (avoid Java OOM exceptions)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Do
• Environment: apollo-99-trunk-20120902.143447-110
• Assignee: Unassigned
• Reporter: Lionel Cons
• Created: 04/Sep/12 06:15
• Updated: 06/Apr/22 19:16
• Resolved: 06/Apr/22 19:16

Description

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...)?