I configured a ProxyConnector nio+ssl transport. When it is used coupled with an external load balancer (over which I have no control at all) I get a quite annoying behavior: the balancer keeps opening connections towards the proxy connector just to assess its responsiveness. The net effect of this is that the memory consumption of the Proxy broker skyrockets. I reproduced the behavior of the balancer with a simple java program that repeatedly opens a series of connection to the proxy connector and then let them dangling (that is, I just shutdown the thread client-side without closing the connection gracefully). Again, the memory consumption of Proxy Broker keeps growing and never decrease. At the end I get more than 6 GB of memory allocated just because of tons of ProxyConnection that are not recycled by the gc. The result is that the ProxyBroker spits out an OOM error.
Mutual authentication is off. I saw these effects both in AMQ 5.8.0 and AMQ 5.9.0. So the questions are: - Is it possible to limit somehow the memory consumption of proxy broker? Apparently the memoryUsage param has no effect. - Why dangling ProxyConnections are not deleted by the ProxyConnector? Is it possible to specify a timeout for them? Thank you for your help! -- View this message in context: http://activemq.2283324.n4.nabble.com/Proxy-Connector-memory-consumption-tp4674255.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
