I noticed, while I was testing a lengthy BPEL process, using a rather generous while loop in term of number of iterations, that the execution stack trace consists in all activities that the BPEL executed so far.
If my while activity iterates a hundred times, and has an inner activity, called A, the after the 99th iteration the execution stack (seen in an exception trace), consists in all 99th calls of A. I think this is not a good idea, since some loops can be quite complex in real life, so the process instance will quickly run out of memory!? I am using BPEL extension alpha4. Let me know if you want a stack trace. /aa View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921474#3921474 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921474 ------------------------------------------------------- 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
