anonymous wrote : | Why do you restrict the MDB's to one node ? | | Deploying them on ALL the same nodes as your SLSB and delegation to a local SLBS from within onMessage() would also loadbalance your message processing ! |
The MDB's are restricted to one node because they listen to a HAJMS DurableTopic if I deploy them to multiple nodes I get JMS exceptions because of duplicate client id's. | javax.jms.InvalidClientIDException: This client id 'blah' is already registered | Unfortunately if I use different client ids on each node the MDB on both nodes process the message, which leads to duplicate requests. I decided to deploy the MDB's on one node. The plan was then to remove most of the logic out of the MDB into SLSB which are load balanced across the cluster. Unless is there some way to have MDB's on multiple nodes listening to a HAJMS DurableTopic? I think Distributed Destinations might supported this but it won't be available to JBossMessaging is complete in JBoss5. Thanks for the warning about the transaction manager not supporting distributed transactions, will have to think about a way round that problem :-( Regards Matt View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872227#3872227 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872227 ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
