"The default behaviour of a join is as you describe it, wait for all tokens to arrive."
This is true, but if you are running the tokens in different threads the join doesn't know about the state from each thread. To make it clearer, think of it this way: each thread is running in a different VM. The cached hibernate objects need to be refreshed at the join so that one VM knows what is going on in the other. ie: when the second thread hits the join, it doesn't know that the first thread hit the join because they are using seperate instances of hibernate objects. The hibernate data must be refreshed prior to executing the join logic so that the join works properly in an asynchronous environment. Does that make my problem clearer? Sean View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911525#3911525 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911525 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
