After looking at the bpmn file it looks like you're missing escalation catch event. You have throwing escalation end event in the sub process but there is no boundary catch event on the sub process so there is no element to catch the escalation event.
Thanks for the response. I now understand that for handling Errors and Escalations a corresponding catch event (event handler) must be provided and the Exception Handler maps the Error/Escalation to the event handler automatically. I was trying to handcode the exception handler using the "Textual Editor" provided for the Exception handler which was causing my confusion. I am able to make the process work by coding the corresponding handler.
Can you upload the fixed / modified Handler and BPMN file. I need to understand the Exception Handler mechanism. Thanks
I have attached the Exception handling code to my post above, it was tested with jBPM v5.1 and shows a very basic exception handling case.
Thanks DME for uploading the Example.
I cant get your example to work with my process. How did you map the signal to the error event with the editor? Is the sub process needed for exception handling?
edit: Ok now it works. But I had to create an embedded subprocess and copy all the meta attributes of your signalEvent into mine (and customize them). But that cant be the way it is meant to be? That is very complicated and not user friendly. So how did you initially map the errorEvent to the signalEvent?
edit2: And i get the following warnings in my console:
(null: 19, 61): cvc-id.2: There are multiple occurrences of ID value 'TestException'.
(null: 19, 61): cvc-attribute.3: The value 'TestException' of attribute 'id' on element 'error' is not valid with respect to its type, 'ID'.
Thank you very much for uploading the example for error handler. It helped me to work on similar problem in my project.