You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/09/09 14:46:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17192916#comment-17192916 ]
ASF GitHub Bot commented on QPID-8448:
--------------------------------------
Dedeepya-T opened a new pull request #59:
URL: https://github.com/apache/qpid-broker-j/pull/59
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> [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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org