[ https://issues.apache.org/jira/browse/AMQ-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated AMQ-4889: --------------------------------- Fix Version/s: 5.10.0 5.9.1 > ProxyConnector memory usage skyrockets when several ssl handshakes fails > ------------------------------------------------------------------------ > > Key: AMQ-4889 > URL: https://issues.apache.org/jira/browse/AMQ-4889 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.8.0, 5.9.0 > Environment: Seen in Windows 7 64bit, Windows Server 2008 R2 and > Linux RHEL 6.3 64 bit > Reporter: matteo rulli > Assignee: Timothy Bish > Fix For: 5.9.1, 5.10.0 > > Attachments: AMQ4889.patch, NIOSSLTransport_patch_AMQ_4889.txt, > ProxyConnIssue.rar, ProxyConnection_patch_AMQ_4889.txt, > ProxyConnector_patch_AMQ_4889.txt, after_lsof.txt, after_netstat.txt, > lsof.txt, netstat.txt, sockstat.txt > > > See > [nabble|http://activemq.2283324.n4.nabble.com/Proxy-Connector-memory-consumption-td4674255.html] > for further details. > To reproduce the issue: > # Start embedded proxy broker and the AMQ broker that are embedded in > *AMQTestBroker* project (see attachments); > # Start the *AMQTestConsumer* project; This program repeatedly tries opening > a connection to the ProxyConnector with wrong certificates. > # Open jconsole to monitor AMQTestBroker memory usage: you should experience > an OOM error within one hour with the suggested settings (Xmx = 2048m). > Launch configurations and test keystores are attached to this issue along > with the java projects. > This behavior seems to affect _ProxyConnector_ only, running the test against > a standard nio-based _TransportConnector_ does not seem to produce anomalous > memory consumptions. -- This message was sent by Atlassian JIRA (v6.2#6252)