I am not able to create new JMS queue in EAP5 server if it uses the same name as JMS queue which was already removed. It is caused that even after JMS queue deletion its .xml file remains in deployment directory of EAP server even though EAP5 server at least in jmx-console no longer knows about the JMS queue. The deployment of JMS queue is made with options=[FailIfExists] and it causes to fail because the file is still there even though it is no longer available in EAP5 server (jmx-console). Steps to reproduce: create through JON ui new JMS queue for EAP5 server, after successful creation delete it. And try to create new JMS queue with the same name. It is not created. The same goes for JMS topic
This seems to be an issue with EAP5. Our code uses the Profile Service APIs to perform the delete operation and counts on it to do the proper clean up. Not sure if we can work around this, because the XML file the queue is defined in is not easily determined. The MBeans (and therefore queues and topics, too) are defined in arbitrarily named files under the deploy dir and EAP5 does not do any direct file modification on them when changing (or deleting) the configurations for individual MBeans. It WILL though create a file called "queue_XXX-service.xml" with the definition of the queue MBean if asked for such creation through the profile service API. A similar delete operation (through profile service API) does NOT remove that file though (only marks given MBean as deleted (in ...data/attachments of the profile directory). Because the AS5 plugin of JON was designed on purpose to solely rely on the management APIs provided by the application server, we don't do any file modifications ourselves. The investment in our plugin required to work around this deficiency in EAP would be significant, because we don't currently have any tools to parse and/or modify the config files of EAP. I've created an EAP BZ 973397 to track this problem on the EAP side.
I spoke too soon in the previous comment. This is something we can fix in JBoss ON.
*** Bug 885617 has been marked as a duplicate of this bug. ***
Fix is going to be part of RHQ 4.9.0, tracked by BZ 973415.
As this is MODIFIED or ON_QA, setting milestone to ER1.
VERIFIED with JON 3.2.0.ER1 and EAP 5.2.0.GA