[
https://jira.jboss.org/jira/browse/JBMESSAGING-1013?page=com.atlassian.ji...
]
Tim Fox closed JBMESSAGING-1013.
--------------------------------
Resolution: Out of Date
Doesn't really apply for JBM 2.0.
Also jbm 2.0 already has extensive management features for copying messages between
queues
Manual merge queue feature via management
-----------------------------------------
Key: JBMESSAGING-1013
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1013
Project: JBoss Messaging
Issue Type: Feature Request
Components: Configuration and Management, JMS Clustering
Environment: Clustering/load balancing
Reporter: Evgueni Smoliar
Assignee: Tim Fox
Fix For: 2.0.0 Beta
In a case of disaster recovery you are obliged always to recover last running cluster
node. Otherwise some messages will remain in the queue waiting for this node to startup.
Idd there is a workaround for this, but it's not always easy to do. Would me much
nicer to have a manual function to merge queues ( or reallocate messages) preferably
available via JMX.
For more detail please check forum.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira