[AMQ-4889] ProxyConnector memory usage skyrockets when several ssl handshakes fails

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.8.0, 5.9.0
• Fix Version/s: 5.9.1, 5.10.0
• Component/s: Broker

Environment

Seen in Windows 7 64bit, Windows Server 2008 R2 and Linux RHEL 6.3 64 bit

• Assignee: Timothy A. Bish
• Reporter: matteo rulli
• Created: 15/Nov/13 09:41
• Updated: 02/Apr/14 22:16
• Resolved: 16/Dec/13 17:14

Description

See nabble for further details.

To reproduce the issue:

1. Start embedded proxy broker and the AMQ broker that are embedded in AMQTestBroker project (see attachments);
2. Start the AMQTestConsumer project; This program repeatedly tries opening a connection to the ProxyConnector with wrong certificates.
3. 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.