Issue

• An application has been migrated from EAP5 to EAP6, but after a little while we see an abnormal behavior and we need to switch back to EAP5: we want to make sure no pending transactions and messages are left in EAP6.
• An application is running on EAP6, but we need to move it to another server with a different name, on a different machine: we want to make sure no pending transactions and messages are left in the original EAP6 server.
• An application is running on a EAP6 cluster, which is too large so we want to decrease the number of instances in the cluster. Before retiring a node we what to make sure no pending transactions and messages are left.
• How to ensure 1) online and 2) offline that:
  • no JTA transactions are pending
  • no JMS messages in any queues
  • no HornetQ transactions are pending