[
https://issues.apache.org/jira/browse/AMQ-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Naseef updated AMQ-4970:
-------------------------------
Attachment: AMQ4970Test.zip
Updated AMQ4970Test.zip so it now tests both the
ActiveMQConnection.destroyDestination() and BrokerView.deleteQueue() methods.
Still not reproducing the problem this way.
Tried another approach (capturing kahadb snapshots):
== part 1 ==
* Clear the kahadb
* Start the broker
* Create two destinations
* Stop the broker
* Take snapshot 1 of the kahadb
* Start the broker
* Remove one destination
* Stop the broker
* Take snapshot 2 of the kahadb
* Start the broker
* Confirm errant operation (removed destination recreated)
== part 2 ==
* Stop the broker
* Clear the kahadb
* Start the broker
* Create 2 destinations
* Remove 1 destination
* Stop the broker
* Capture snapshot 3 of the kahadb
* Start the broker
* Confirm correct operation (destination remains removed)
Comparing Snapshots 2 and 3, there are differences (as expected):
* The db.redo file contains the removed destination name in the errant process
path.
* The db.redo file in the normal path does not contain the removed destination
name.
* And the normal path has a db.free file.
* The errant path does not.
I'm wondering if something in the out-of-the-box configs differing from the
internal broker in the AMQ4970Test is contributing to the problem.
Any ideas would be welcome.
> Deletion of a queue inaffective across broker restart
> -----------------------------------------------------
>
> Key: AMQ-4970
> URL: https://issues.apache.org/jira/browse/AMQ-4970
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.9.0
> Environment: mac osx/mavericks
> Reporter: Arthur Naseef
> Attachments: AMQ4970Test.zip, AMQ4970Test.zip
>
>
> Deleting a queue, it is revived from persistent store after a broker restart.
> The following steps reproduce the problem:
> * Create a queue (confirmed using the REST client I/F)
> * Shutdown the broker
> * Startup the broker
> * Confirm queue still exists via the hawtio ui (correct operation so far)
> * Delete the queue
> * Confirm queue removed via the hawtio ui
> * Shutdown the broker
> * Startup the broker
> * Confirm queue was not recreated via hawtio ui (failed: queue still exists)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
