[ 
https://issues.apache.org/jira/browse/QPID-8157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703027#comment-16703027
 ] 

ASF subversion and git services commented on QPID-8157:
-------------------------------------------------------

Commit d33550bd32fe76aec1ea1f0444294e0d24121460 in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=d33550b ]

QPID-8157: Make sure that on deletion of configured object the references to 
the object from various tasks, executors, listeners, etc are removed as well


> [Broker-J] Deletion of Virtual Host Node fails to clean-up properly all 
> Virtual Host/Virtual Host Node resources
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-8157
>                 URL: https://issues.apache.org/jira/browse/QPID-8157
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-7.1.0
>            Reporter: Alex Rudyy
>            Priority: Major
>             Fix For: qpid-java-broker-7.1.0
>
>
> Deletion of BDB HA Virtual Host Node ends up in left behind configuration and 
> coalescing committer threads, open amqp connections, etc
> Steps to reproduce
> * Create BDB HA Virtual Host Node using management
> * Delete BDB HA Virtual Host Node using management (preferably amqp 
> management)
> * Collect heap dump and check references to deleted  virtual host node
> {noformat}
> select * from 
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImplWithAccessChecking
> {noformat}
> Only master sources are affected by the issue. It seems one of recent 
> refactoring of delete functionality introduced the regression.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to