"schrouf" wrote : 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. | | | Ok, what about the following two-step approch: | | The MDB with a durable subscription to your JMS topic (restricted to one node due to the unique client ID requirement) simply forwards each received message to an 'internal' processing queue (let's call this MDB message forwarder). | | These messages then can be processed (without duplicates) by a second MDB () deployed on ALL nodes (let's call these MDB's message processors). | | You would gain perfect loadbalacing AND transactional safety at the cost of an additonal JMS message send operation. | | As the processing is anyway asynchronous this shouldn not be a real problem in most cases :-) | | Regards | Ulf |
I had considered this approach but was trying to use just the one set of MDB's listening to a DurableTopic. Anyway decided to use this two step approach of a topic with mdb's forwarding the message onto a queue, etc. Which I now have working with load balancing, failover,etc. Thanks for all your help. Matt View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872420#3872420 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872420 ------------------------------------------------------- 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-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
