[QPID-8448] [Broker-J] Http connection objects are leaked on HTTP port with a support for both TLS and TCP transports

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: qpid-java-broker-8.0.0
• Fix Version/s: qpid-java-broker-8.0.1, qpid-java-broker-7.1.9
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Alex Rudyy
• Created: 23/Jun/20 21:57
• Updated: 19/Sep/20 17:50
• Resolved: 14/Sep/20 08:02

Description

When HTTP port is configured with a support for TLS and non-TLS transports, the factory TlsOrPlainConnectionFactory is used to create instances of TlsOrPlainConnectionFactory$PlainOrTlsConnection. The established HTTP connections are registered in map HttpManagement$ConnectionTrackingListener#_closeFutures. However, TLS connection objects are not removed from the map on their close and remain referenced until broker is restarted. With frequent REST API calls the leaked connection objects can cause OOM.

The issue only affects TLS connections. The non-TLS connection do not cause memory leak.
The issue could be worked around by configuring only TLS transport (or only TCP transport) on the HTTP port.