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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: qpid-java-broker-7.0.0
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 28/Sep/17 13:03
• Updated: 27/Aug/18 08:54
• Resolved: 09/Oct/17 15:54

Description

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.

Issue Links

• relates to: QPID-8229 [Broker-J][6.x] Queue bindings are not removed on queue deletion when BDB/DERBY/JDBC configuration stores are used