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 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872314#3872314 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872314 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
