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 2018/06/04 09:16:00 UTC

[jira] [Updated] (QPID-8157) [Broker-J] Deletion of Virtual Host Node fails to clean-up properly all Virtual Host/Virtual Host Node resources

     [ https://issues.apache.org/jira/browse/QPID-8157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Rudyy updated QPID-8157:
-----------------------------
    Fix Version/s: qpid-java-broker-7.1.0

> [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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org