[jboss-user] [JBoss jBPM] - Re: TaskInstance.end() hogs CPU time

2007-01-18 Thread Johan.Parent
No progress with this problem! I ran the Websale example with more success so I guess the problem resides in the way I have defined the identities or the assignment(s) then. After all the hibernate code that eat up all the time relates exactly to this. | identity | !-- 2 doctors -- |

[jboss-user] [JBoss jBPM] - Re: TaskInstance.end() hogs CPU time

2007-01-11 Thread Johan.Parent
Hi Koen, Many thanks for your answer! You're are right of course, below the relevant code and definition. I've run into the exact same problem using a HSQLDB as well as a Sybase backend. The process definition is (IMHO) simple: | ?xml version=1.0 encoding=UTF-8? | | process-definition

[jboss-user] [JBoss jBPM] - Re: TaskInstance.end() hogs CPU time

2007-01-11 Thread [EMAIL PROTECTED]
Johan, This client method is part of another loop, I presume? Are you creating more than one JbpmConfiguration outside this loop? The only thing that you should change is to create the context within the try-finally block instead of before it. But the rest of your process/code combo looks

[jboss-user] [JBoss jBPM] - Re: TaskInstance.end() hogs CPU time

2007-01-11 Thread Johan.Parent
Koen, The method was initially in a loop, but since it is supposed to handle all the instances it only called once in my test program. I initialize the jbpmcConfiguration like this: | static JbpmConfiguration jbpmConfiguration = JbpmConfiguration.getInstance(); | I'll follow your