activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin W Edwards (JIRA)" <>
Subject [jira] Commented: (AMQ-2023) BrokerViewMBean.removeQueue does not clean up advisory topics
Date Wed, 10 Jun 2009 16:11:35 GMT


Kevin W Edwards commented on AMQ-2023:

We are using the mbean operation RemoveTopic to remove dynamically created topics when they
are no longer needed.

If the dynamic topic is named "TestTopic" our current work around is to call RemoveTopic with
the following:




Our tests work as expected... will update if I find any negative side-effects

> BrokerViewMBean.removeQueue does not clean up advisory topics
> -------------------------------------------------------------
>                 Key: AMQ-2023
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0, 5.2.0
>         Environment: Windows XP JDK 1.5, Ubuntu 8.10 JDK 1.6
>            Reporter: Aaron Riekenberg
>         Attachments:
> Using BrokerViewMBean.removeQueue to remove a queue does not clean up advisory topics
for the queue.
> It appears to be possible to manually remove advisory topics for the queue after the
queue has been deleted using removeTopic, but this should not be necessary according to the
> Steps to reproduce (bug happens on 5.1.0 and 5.2.0):
> 1. Run TestSubscriber to create a queue named TestQueue.
> 2. Observe in JConsole that queue TestQueue and advisory topic ActiveMQ.Advisory.Consumer.Queue.TestQueue
now exist.
> 3. In JConsole invoke removeQueue on the BrokerViewMBean with the parameter TestQueue.
> 4. Observe the queue TestQueue is removed, but the advisory topic ActiveMQ.Advisory.Consumer.Queue.TestQueue
still exists.
> This also happens when invoking BrokerViewMBean.removeQueue programatically.  There are
no message sent over TestQueue in the steps above, but this also appears to happen after messages
have been sent over the queue.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message