Almost ;) Transactions from the same origin must be processed in sequence. Transactions from different origins can be processed i parallell.
So the threads must be coordinated to avoid working on the same origin at the same time. Anyway, I have solved this now by using one scheduler that populates a java.util.concurrent.BlockingQueue. My worker threads feed of the blockingqueue, and the swchedulerwaits for all threads to die before finishing. Unless starting threads from my scheduler should be avoided, I believe this is a simple solution. -Karl Ivar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913068#3913068 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913068 ------------------------------------------------------- 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
