[
https://issues.apache.org/jira/browse/AMQ-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875232#comment-13875232
]
Arthur Naseef commented on AMQ-4970:
------------------------------------
Huh, that's interesting Timothy. I wonder what's different. I'm working with
a version of the trunk that can't be more than a couple of weeks old. I'm
running this on a mac. I think jdk 1.7 - need to verify.
With a little debug logging, I see that the task for expiring messages
continues to be called even though the cancel method is called on the scheduler
for the task. I haven't had a chance to do any more than that today due to
other priorities.
> 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, 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)
