The queue needs to be manually destroyed after undeployed. Undeploy will only destroy the JMS part (which is basically the JNDI). It won't destroy the queue itself as that could mean losing valid data. It was a design decision. (Undeploy != destroy).
Tom, is this actually an issue or just digfferent to how JBM works?
Hey Andy... I guess it depends on what's behind those MBeans that remain listed in the JMX console.
As you'd know... 2 beans are added when a queue is deployed... one for the JMS bits and one that seems to be related to the core hornetq destination. When I removed/undeployed the queue from the hornetq-jms.xml file and added a new one, both beans relating to the previous queue remained listed in the console. Shouldn't at least the JMS related bean be removed? When I did a restart, the JMS related bean for the previous queue did get removed. Does this suggest a potential issue?
Maybe it's a bit confusing listing any of these beans in the JMX console after the destinations have been removed from all user configs? I think Clebert was suggesting removing them if there were no messages left in them, which seems to make sense.
I'm having the same issue currently. A quick scan of the HornetQ documentation gives some information on deleting queues, but only in reference to the queues managed via the admin-console. None of my queues display in the admin-console.
When I simply added/removed queues to/from the xml as you described, the list grows to become the union of all the queues I've ever created.
Help? How do I remove these?
I just stumble upon this thread, and want to share the twiddle command to destroy the queue
Or you can do it in jmx-console.