[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1300) Non-Remote JMS HA
[ http://jira.jboss.com/jira/browse/JBAS-1300?page=comments#action_12314737 ] Adrian Brock commented on JBAS-1300: One week is a joke of an estimate. But then yet again (despite you posting this about three times in the forums and me correcting you on every occasion) you have left off the hard work from your description: 1) Persistent connections http://jira.jboss.com/jira/browse/JBMQ-14 2) Using the DB (persitent store) as more than just a recovery log http://jira.jboss.com/jira/browse/JBMQ-12 3) Reliably distributing work across multiple machines in the same transaction http://jira.jboss.com/jira/browse/JBMQ-5 For your requirements, (3) would also have to include correct processing of failed transactions on failover. Another usecase of (3) is to have topic subscriptions distributed across multiple machines where the client can send to any machine, but the individual subscriptions are distributed across multiple machines (with the servers communicating to balance how many clients they have connected). 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, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1300) Non-Remote JMS HA
[ 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, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1300) Non-Remote JMS HA
[ http://jira.jboss.com/jira/browse/JBAS-1300?page=comments#action_12314739 ] Andrew Oliver commented on JBAS-1300: - There is like next to no way I posted about this 3 times in the forums. :-P Is the new messaging not called JBossMQ? I'm only concerned about the ends not the means really. 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, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1300) Non-Remote JMS HA
[ http://jira.jboss.com/jira/browse/JBAS-1300?page=comments#action_12314741 ] Adrian Brock commented on JBAS-1300: This is the wrong place for this argument... But, here is one example where I complained I've said this many times before... http://www.jboss.org/index.html?module=bbop=viewtopict=44218start=20 and here's a couple of threads where these issues keep popping up (there are plenty of others including a discussion I remember with you but I couldn't easily find using search - it might not have been in the forums?). http://www.jboss.org/index.html?module=bbop=viewtopict=54737 http://www.jboss.org/index.html?module=bbop=viewtopict=53157 And for reference here's some discussions back when HAJMS was first implemented and why HAIL was wrong: http://www.jboss.org/index.html?module=bbop=viewtopict=38189 http://www.jboss.org/index.html?module=bbop=viewtopict=42786 There are plenty of similar discussions in the both the dev and user forums. Just to repeat my objections in plain terms: If we are going to implement transparent failover for HAJMS it cannot just be a best effort. People use JMS for reliable messaging. If they configure guaranteed only once delivery they expect exactly that. 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
