[
https://issues.apache.org/jira/browse/QPID-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010016#comment-13010016
]
Danushka Menikkumbura commented on QPID-3162:
---------------------------------------------
When I investigate I see a number of references (some are circular) among some
transport-level objects like MINANetworkDriver, Connection,
ProtocolEngine_0_10, etc which prevent the objects from getting GC'ed. Also
there is a synchronisation issue in closed() method in
org.apache.qpid.transport.Connection that occurs when it tries to set
connection state to CLOSED that in turn prevents corresponding
ProtocolEngine_0_10 object from getting removed from the _typeMap in
org.apache.qpid.server.configuration.ConfigStore eventually. Hence a memory
leak per connection.
> Memory leak in Java Broker when large number of connections created
> -------------------------------------------------------------------
>
> Key: QPID-3162
> URL: https://issues.apache.org/jira/browse/QPID-3162
> Project: Qpid
> Issue Type: Bug
> Reporter: Danushka Menikkumbura
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]