[ http://jira.jboss.com/jira/browse/JBAS-1300?page=history ]
Scott M Stark updated JBAS-1300: -------------------------------- Assign To: (was: Scott M Stark) Priority: Minor (was: Major) > 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 > Priority: Minor > > 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 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development