EJB timer stops working (for example when timer start event is used) on specific circumstances.
The issue was observed on Kie server for this scenario:
1) Container using Per process instance strategy with a process using timer (for example in intermediateCatchEvent) is created, process is started, timer is updated to some short time span, process is finished, container is deleted.
2) Container with singleton strategy is created, updated to the broken kjar (for example it contains malformed kie-deployment-descriptor), container is kept active on Kie server.
3) Container with timer start event is created
Timer start event is not fired.
There is no error or stacktrace visible in server log (except of expected stacktrace when container is updated to broken one).
Reproduced on WildFly, WebLogic and WebSphere. Works without issues on Tomcat and Springboot.
The reproducing scenario is quite complicated, will provide a reproducer in a form of Kie server integration test.
Reproducer is available in https://github.com/kiegroup/droolsjbpm-integration/pull/1647