Brilliant! Many thanks Gary - v5.5.0 fixed the issue.
If you have time, I'd be very interested to read the JIRA should you find
it.
Great work, and thanks for the response.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Memory-Leak-In-TransportConnector-tp3635116p3637273
Hi All
I have a Java application (A) with 4Gb of heap using an embedded broker
(v5.3.1). I have a second application (B) also containing a broker.
Messages are sent to broker A which auto-forwards them to broker B. We use
this setup for fault tolerance. We want to be able to continue to run A
