[ http://jira.jboss.com/jira/browse/JBAS-1300?page=comments#action_12314738 ] Adrian Brock commented on JBAS-1300: ------------------------------------
Since this is work being done in the new JMS, it is unlikely to get implemented within JBossMQ. > Non-Remote JMS HA > ----------------- > > Key: JBAS-1300 > URL: http://jira.jboss.com/jira/browse/JBAS-1300 > Project: JBoss Application Server > Type: Feature Request > Components: JMS service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final > Reporter: Andrew Oliver > Assignee: Scott M Stark > > Original Estimate: 1 week > Remaining: 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
