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 2016/02/19 14:30:18 UTC
[jira] [Created] (QPID-7082) [Java Broker] Closed Connection and
Session objects can be leaked via AccessControlContext object referenced
from Queue#_immediateDeliveryContext
Alex Rudyy created QPID-7082:
--------------------------------
Summary: [Java Broker] Closed Connection and Session objects can be leaked via AccessControlContext object referenced from Queue#_immediateDeliveryContext
Key: QPID-7082
URL: https://issues.apache.org/jira/browse/QPID-7082
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: qpid-java-6.0, qpid-java-6.0.1
Reporter: Alex Rudyy
Instance of AccessControlContext referenced from Queue#_immediateDeliveryContext is created from an existing AccessControlContext on queue creation. If queue is created via messaging layer, the existing AccessControlContext can hold references to ConnectionPrincipal and SessionPrincipal and their connection and session object accordingly. As result, Queue#_immediateDeliveryContext can refer ConnectionPrincipal and SessionPrincipa prebeting garbage collection of corresponding AMQPConnection and AMQSessionModel objects for the duration of the queue life.
With lots of long lived queues that were created by lots of different connections the broker memory consumption might grow in time and eventially Broker can run OOM if not bounced.
It seems we do not need to refer an existing AccessControlContext from any system AccessControlContext.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org