I added a tentative patch to the issue (AMQ-4889).
As long as I can see, the problem was adding ProxyConnection objs into a
collection inside ProxyConnector before starting them.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Proxy-Connector-memory-consumption-tp46742
Ok, issue created: AMQ-4889
I attached to the issue a couple of simple projects to reproduce the issue.
Apparently this issue affects the ProxyConnector only, not the standard
TransportConnector.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Proxy-Connector-memory-con
it would be awesome if you could put together a little unit test that
shows this and open a jira. then we can fix it asap.
take some inspiration from the tests here:
https://github.com/apache/activemq/tree/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/proxy
On Wed, Nov 13, 2013 a
Nobody?
Is the question so boring?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Proxy-Connector-memory-consumption-tp4674255p4674390.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.