activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "matteo rulli (JIRA)" <>
Subject [jira] [Updated] (AMQ-4889) ProxyConnector memory usage skyrockets when several ssl handshakes fails
Date Fri, 29 Nov 2013 11:34:35 GMT


matteo rulli updated AMQ-4889:

    Attachment: after_netstat.txt

> ProxyConnector memory usage skyrockets when several ssl handshakes fails
> ------------------------------------------------------------------------
>                 Key: AMQ-4889
>                 URL:
>             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, ProxyConnector_patch_AMQ_4889.txt,
after_lsof.txt, after_netstat.txt, lsof.txt, netstat.txt, sockstat.txt
> See [nabble|]
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
> 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

View raw message