Description of problem: When you create a process with Signal Start Event, beforeProcessStarted and afterProcessStarted are called twice. Version-Release number of selected component (if applicable): 6.1.0 ER2 Steps to Reproduce: 1. Create a simple process which contains only Signal Start Event and End Event. 2. Create your own ProcessEventListener and add it to the KieSession. 3. Start the process and see generated events. 4. Send a signal and see another events. Actual results: Both beforeProcessStarted and afterProcessStarted methods are called twice. Once when you call ksession.startProcess and then again when you send a signal and process is really started. Expected results: I think the correct behavior will be if both beforeProcessStarted and afterProcessStarted are called just once. After you call ksession.startProcess, beforeProcessStarted should be called. And after the signal is sent, afterProcessStarted should be called. Additional info: http://git.app.eng.bos.redhat.com/git/jbossqe/brms.git/tree/test-jbpm-regression/src/test/java/com/bpms/functional/ProcessEventListenerTest.java http://git.app.eng.bos.redhat.com/git/jbossqe/brms.git/tree/test-jbpm-regression/src/test/resources/SignalStartEvent.bpmn2
Tomas, for signal start event there is no need to call start process because it should be started by signal and not manually. In your case it actually starts two process instances you can see that when you print out process instance id from within listener.
Oh, I have not realized that I run two process instances. Thanks for the explanation, it makes sense now. I am closing this BZ as it is not a bug.