[jira] [Commented] (AMQ-4889) ProxyConnector memory usage skyrockets when several ssl handshakes fails

["Timothy Bish (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839036#comment-13839036 ] 

Timothy Bish commented on AMQ-4889:
-----------------------------------

I've reviewed the attached patches, looks pretty good.  I applied the fix to the NIOSSLTransport.  The equals method in the ProxyConnection looks a bit odd, think maybe the equals comparison might be backwards.  I updated the fix a bit with some additional changes.  You should take a look and test in your setup.  Would be great if you can boil down the tests into a JUnit test of sorts so we can see if things are working as expected.  

> 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
>         Attachments: 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.1#6144)