You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "matteo rulli (JIRA)" <ji...@apache.org> on 2013/11/15 10:43:22 UTC
[jira] [Created] (AMQ-4889) ProxyConnector memory usage skyrockets
when several ssl handshakes fails
matteo rulli created AMQ-4889:
---------------------------------
Summary: 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.9.0, 5.8.0
Environment: Seen in Windows 7 64bit, Windows Server 2008 R2 and Linux RHEL 6.3 64 bit
Reporter: matteo rulli
Attachments: ProxyConnIssue.rar
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)