This is being pretty annoying on my tests, so I have commented out the destroyQueue call for now: | public void undeploy(final Node node) throws Exception | { | if (node.getNodeName().equals(CONNECTION_FACTORY_NODE_NAME)) | { | String cfName = node.getAttributes().getNamedItem(getKeyAttribute()).getNodeValue(); | jmsServerManager.destroyConnectionFactory(cfName); | } | else if (node.getNodeName().equals(QUEUE_NODE_NAME)) | { | String queueName = node.getAttributes().getNamedItem(getKeyAttribute()).getNodeValue(); | //TODO: https://jira.jboss.org/jira/browse/JBMESSAGING-1413 | //jmsServerManager.destroyQueue(queueName); | } | else if (node.getNodeName().equals(TOPIC_NODE_NAME)) | { | String topicName = node.getAttributes().getNamedItem(getKeyAttribute()).getNodeValue(); | //TODO: https://jira.jboss.org/jira/browse/JBMESSAGING-1413 | //jmsServerManager.destroyTopic(topicName); | } | } | I'm not sure how undeploy should work here. I will let this for Jeff or Andy to deal with that. ATM https://jira.jboss.org/jira/browse/JBMESSAGING-1413 is with Jeff. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173423#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...