Hello again. I said i was going to test your asynchronous idea but i'm sorry i can't reproduce the problem again when synchronous.. I must have changed something somewhere. "bstansberry(a)jboss.com" wrote : | You'd have to do something like what people do with JMS temporary queues to turn an asynchronous messaging system into something synchronous;. i.e. execute your commands on a different thread but have that thread at the end send a message to the node that initiated the process telling them it's complete. The node that initiates the process blocks waiting for those messages to come in. | Complex. Yuck. Let's find a better way. | Yeah it could work but i would rather not do that.. anonymous wrote : | The JGroups channel guarantees that the application will receive messages in the order sent. You can't guarantee that if you allow multiple threads to deliver messages. | | JGroups 2.6 (used in AS 5) improves on the single-threaded JG 2.4 architecture by having a thread pool to carry messages up, but it still only allows one thread at a time per sender to be delivering messages to the application. So wouldn't help with your problem. | Ah i see. anonymous wrote : | Yes, because AS 5 uses JBoss Messaging instead of JBossMQ. No more JMS server only running on one node. Instead your topics and queues are deployed on every node. So there would be no need for HA-JNDI to make a group RPC to find the JMS resources; they would be bound locally. | | BTW, you can install JBoss Messaging in 4.2.3 as well. See the JBoss Messaging project pages. Perhaps that's your solution. Hm, i sort of want to try it now. I'm going to read about it a bit before i decide if it's not too tough to migrate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205479#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...