In our project, we have a requirement of taking an auto-decision for a user task if the user is not closing this task in the given duration.
Technical implementation will have a user task and a timer boundary event attached to it. In order to cancel the user task upon timer expiry, below settings have been made(Cancel activity has been turned on).
The below flow works fine as long as there are no execution listeners(or invoking any java class through java service task) after timer boundary event, else an exception is thrown in the timer job and the error is :
“could not instantiate the class(the class invoked in execution listener of service/user task or any sequence flow which are called after timer boundary event)”.
Please note the same user task is at the beginning of the flow, and we are able to execute it’s listener successfully. After timer boundary event is fired, somehow the execution context is lost or not being supported.
Regarding process engine configuration, turning ‘JobExecutorActivate’ on is not making any difference , so it has been turned off and settings in the attached document has been followed.
ya, the CLASS is in classpath and also, if I call any Listener class before TIMER it can able to execute the listener. Only when it comes after the TImer which has "CancelActivity = true" it fails to instantiate the class on the listener