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 subversion and git services (JIRA)" <ji...@apache.org> on 2017/10/09 15:55:00 UTC

[jira] [Commented] (QPID-7933) [Java Broker] Changes made to existing durable children of virtualhost not recorded to the configuration store after a virtualhost restart

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

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

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

QPID-7933: [Java Broker] Ensure changes made to existing durable children of virtualhost after virtualhost restart are persisted


> [Java Broker] Changes made to existing durable children of virtualhost not recorded to the configuration store after a virtualhost restart
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-7933
>                 URL: https://issues.apache.org/jira/browse/QPID-7933
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Keith Wall
>             Fix For: qpid-java-broker-7.0.0
>
>
> If a *virtualhost* is stopped, the object's children are closed and evacuated from memory.  On restart, the children are recovered from the store.   However, the restart path AbstractVirtualHost#onRestart fails to reinstall the StoreConfigurationChangeListener on the recovered children.   The effect of this is that subsequent changes made to *existing* durable children (for instance, a queue's alert threshold) are not persisted to the configuration store.   
> The persistence of newly added objects (or the deletion of existing objects) is not affected.  This is because the VirtualHost still has its StoreConfigurationChangeListener intact.  (The virtualhost is not closed during a restart).
> A restart at the virtualhostnode level does not suffer this problem.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org