You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (Jira)" <ji...@apache.org> on 2020/06/23 21:59:00 UTC
[jira] [Updated] (QPID-8448) [Broker-J] Http connection objects are
leaked on HTTP port with a support for both TLS and TCP transports
[ https://issues.apache.org/jira/browse/QPID-8448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-8448:
-----------------------------
Environment: (was: 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.)
> [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
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org