Esteban Aliverti [https://community.jboss.org/people/eaa] created the discussion "Re: JBPM stuck when reach AdHocSubprocess and stop executing when reach IntermediateThrowEvent" To view the discussion, visit: https://community.jboss.org/message/718997#718997 -------------------------------------------------------------- Some anwers and remarks: * Process are executed in the same thread your application is running, so doing a while (!mKSession.getProcessInstances().isEmpty())  waiting for something is useless. * In the case of ad-hoc processes, you need to manually signal the node you want to execute using ksession.signalEvent(). I think you will have to take a look at the tests that shown the behavior of ad-hoc processes in order to get an idea in how to use them. So, the behavior you are experiencing here is the expected. jBPM5 is waiting for someone to signal the node to execute. Your app will be forever in the while() loop. Maybe for your case you can use an embedded subprocess instead of an ad-hoc subprocess. * In the case of the intermediate escalation throw event, it seems a bug in jBPM5. Even if nobody is catching that event, the execution should always continue. But maybe I'm wrong here and some of the core developers can correct me. Best Regards, -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/718997#718997] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]