No, I mean that we had to drop MDB load balancing altogether and deploy the MDB as ha-singleton (the EJB jar). The actual message queue is always ha-singleton, I think.
We had very limited time to solve this so didn't have time to research what's causing this... IIRC, in JBoss 4.0.3 sp1 this worked ok, but other clustering problems there prevented our upgrade. If you have the possibility, you could try 4.0.4..? But really I don't know what this was... Could even be some configuration error. And if you find a solution, I'd be willing to know... ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938142#3938142 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3938142 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
