Some more info,
I removed any definition of my queue from hornetq-jms.xml and defined the queue in hornetq-configuration.xml
Then the queue appears correctly in JMX jConsole with the durable attribute as false. However I had to delete the hornetq distro re unzip the distro and start the server with the new queue definition as above before it appeared correctly in the JMX jConsole. It seams like there is some kind of persistent caching going on with regards to the JMX management view.
If you initially created the queue durable then it would have been persisted in the bindings journal, meaning it would get reloaded when the server re started. Delete the journal and you should see normal behaiviour.
Ah, great thanks, indeed I am seeing normal behavior now.
Yep, once a durable queue has been created you can't make it undurable or delete by changing hornetq-jms.xml - this is to prevent people making mistakes and accidentally deleting all their data.
Queues need to be deleted via the management console, or programmatically using the core or management apis.
Just not declaring an already created queue in hornetq-jms.xml does not delete. The list of queues in hornetq-jms.xml is just the subset of queues which you wish to put into JNDI on startup, it is not an exhaustive list of queues.