This could be http://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8180048, a memory leak in G1. If so you can work around it by switching to concurrent mark sweep or you can upgrade to the very latest Java SE 8u144 from Oracle, where the bug should be fixed. Not sure if the fix is in OpenJDK yet. Alternatively you could enable native memory tracking (not in production!) and check if it is the symbol area that grows, more specifically from interned strings.
-Erik -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
