We encountered the memory leak being described (the client map in HttpTunnelServlet). In our case, we had an HTTP-based network of brokers on an unreliable network. The brokers would constantly reconnect to each other and eventually the client map caused an OOM.
I've reported the issue and included a patch: https://issues.apache.org/activemq/browse/AMQ-3021 -- View this message in context: http://activemq.2283324.n4.nabble.com/HTTP-Broker-Transport-Holding-Dead-Connections-tp2354941p3029545.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.