[
https://issues.apache.org/jira/browse/QPID-8448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193250#comment-17193250
]
ASF subversion and git services commented on QPID-8448:
-------------------------------------------------------
Commit 5c2274f8d1d45f442b82d91ca1a247cfe9f76688 in qpid-broker-j's branch
refs/heads/master from Dedeepya T
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=5c2274f ]
QPID-8448: Make sure that actual connection is closed
This closes #59
> [Broker-J] Http connection objects are leaked on HTTP port with a support for
> both TLS and TCP transports
> ---------------------------------------------------------------------------------------------------------
>
> Key: QPID-8448
> URL: https://issues.apache.org/jira/browse/QPID-8448
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-8.0.0
> Reporter: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-broker-8.0.1
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
