Hi guys, sorry for the panic, but I was working against the clock and willing to take any humiliation connected with stupid questions :-) Speed was all that mattered.
What surprised me was that it was tested code that threw up this problem. I was just playing around with some very rare scenarios in the lull before final deployment and all of a sudden it goes doom! I haven't yet figured out what caused the change (and it wasn't realy a priority.) No there is nothing you should(!) do in jBPM code as the flushing is correct behaviour if you take 2 minutes to think about it, but thanks for asking. The root cause of the problem was my 'magic' adding transient runtime actions to the processInstance on the fly. I remove all instances + the corresponding logs before saving the processInstance, but that wasn't enough or rather soon enough in this case. You missed out on a case of beer though. That would have been the next level of coaxing :-) Greetings Rainer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919471#3919471 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919471 ------------------------------------------------------- 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
