[jboss-user] [jBPM] - Re: NullPointerException problem when console tried to start new sub process, triggered by signal sent from async task

Bruce Cui [http://community.jboss.org/people/brucecui] created the discussion "Re: NullPointerException problem when console tried to start new sub process, triggered by signal sent from async task" To view the discussion, visit: http://community.jboss.org/message/613363#613363 -------------------------------------------------------------- Hi Kris, Thanks a lot for the clarification. I am using the ksession which is injected when the WorkItemManager registers the handler. I'll keep digging on the direction you showed me. But last change took me almost a whole weekend. If you could help with the code change this time that would be great. Plz let me know if I need to open a JIRA for that. Or, as long as the console could keep functioning, if there is a way to turn off JPA that would be a secondary option for me, since for now persistence is not a necessary feature for my needs. And for the second question, I think you've answered it even with my poor expression. So if I undersatnd right, even the process is defined as an infinite loop, if in the loop it calls an async task first and then comes to a wait state by a signal event node, the thread will return, and the rest of the loops will be handed to the next signalEvent caller thread, and so goes on. The reason I asked this was becasue I worried about if the old threads didn't return, there would be more and more threads accumulated in similar scenario and finally ate up all resources. But if it works in the way you explained, there should be no problem. Bruce -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/613363#613363] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]