Hi Raj, correct, you will not achieve true Java concurrency with a fork. This is discussed in some detail in various Threads here. There are some very good reasons for jBPM not to start threads.
jBPM implements concurrency in a business process sense, not in a Java multithreading sense. This shouldn't be a real problem. For long running actions you can always spawn real threads by way of async execution (JMS, etc.). Greetings View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923046#3923046 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923046 ------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
