[jboss-jira] [JBoss JIRA] Closed: (JBAS-1300) Non-Remote JMS HA
[ http://jira.jboss.com/jira/browse/JBAS-1300?page=all ]
Adrian Brock closed JBAS-1300.
------------------------------
Resolution: Deferred
Closing features that are (or will be) implemented in JBoss Messaging.
http://jira.jboss.com/jira/browse/JBMESSAGING
If anybody wants to provide a patch that implements these,
the issue can be reopened.
Duplicates of these issues will be closed
unless they provide an implementation/patch.
Patches should first be discussed in the
development forum:
http://www.jboss.com/index.html?module=bb&op=viewforum&f=153
if there isn't already a forum link attached to this issue.
Non-Remote JMS HA
-----------------
Key: JBAS-1300
URL: http://jira.jboss.com/jira/browse/JBAS-1300
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
Priority: Minor
Original Estimate: 1 week
Remaining Estimate: 1 week
It should be possible to use JMS on all servers in a cluster with HA enabled. Meaning:
1. Database as a store. Everyone node uses shared DB.
2. JMS_MESSAGES table includes node name
3. In the event of group membership changes another node picks up the old node's
messages
4. JMS Client proxy autofails to another node
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira