Thank you for your response and the link you gave me.
But I think I am missing something because I cannot see how this link/page answers my question.
My main question is, is it valid to start a separate process in my catch block of the ActionHandler?
This new process has 1 task node (async) so a user can take some corrective action and later on signal the process to continue.
With kind regards,
Sorry, the article was about escalation, not exception.
In the execute method a transaction is active, so I would not do long running things. If you want exceptions handled on a process level, I'd model those in the process as far as possible (since they have business consequences). What you could do is move set e.g. a processvariable with the name of that specific state, move the token to an 'exception handling task' and when finishing that task, move the token back to the original node.
Thanks for the reply.
I am aware that the execute is done in a transaction; that's the reason I have an async tasknode in the proces to be started.
I want to create a separate 'Generic Error Handling'-process for all processes; the exceptions I am talking about here are not Business Exceptions but real technical exceptions like 'Database is temporarly offline'.
That's why I do not want to model it in my proces.
Also if I model it in all my processes, I have to connect all nodes to the Generic Error Handling task.
Technically it is all working in my test environment but I wonder if Exception Handling like this is done before and if it feasable in production environments because I do not find much information about this topic (Exception Handling in JBPM) on the web.