leo li [http://community.jboss.org/people/leo87601] created the discussion "Re: [jbpm5.1]Can get the current nodeId,correctly??" To view the discussion, visit: http://community.jboss.org/message/645334#645334 -------------------------------------------------------------- Thank you for you relpy Salatino. ksession.getWorkItemManager().completeWorkItem(workItemId, results); ksession.getWorkItemManager().abortWorkItem(workItemId); That's a mistaken by our developer. I had fixed it before. Here is the backgroud of this project. We are developing a web application with JBPM5.1, we might have a few "startProcess" and "completeWorkitem" requests at the same time. We have using Jmeter simulate our pressure ,10 concurrency user request on the same time. At the beginning,we using the persistence implementation,we try to create a Ksession for every request and dispose() every time, we found nearly 50% error on the JBPM db(the Error case the same my first post).The error scenario is the workflow stay at the last status and cannot be completed, evan it shown Qualified  in log table, but our when we using the API to check the process instance, it still Pending. We have no idea to fix those data and these kind of data also be found on ur UAT environment(withoutsimulateion testing) . After that we try to made the Ksession as a singlton object as my second post. The problem had been fixed. we can past the 10 concurrency user Jmeter testing. For the how to use the Ksession, what's the best implementation way if we using persistence? 1. Does the Ksession should be shared for different requests  ?  Or we should created different Ksession for different process instance? 2. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/645334#645334] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]