-
Bug
-
Resolution: Done
-
Major
-
7.3.0.GA
There's an unexpected EJB Timer error in server.log when redeploying project in development mode (using the 'Deploy' button only).
Important aspect of the issue is that there's an active process when redeploying.
See steps to reproduce.
See also full server.log in attachment.
WARN [org.jbpm.services.ejb.timer.EJBTimerScheduler] (EJB default - 6) Execution of time failed due to Runtime manager evaluation_1.0.0-SNAPSHOT is already closed: java.lang.IllegalStateException: Runtime manager evaluation_1.0.0-SNAPSHOT is already closed . . . ERROR [org.jboss.as.ejb3.timer] (EJB default - 6) WFLYEJB0020: Error invoking timeout for timer: [id=b37a6b61-35e4-461b-bfc5-ab2967e0e562 timedObjectId=kie-server.kie-server.EJBTimerScheduler auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@3714a9d0 initialExpiration=Thu Mar 14 15:32:40 CET 2019 intervalDuration(in milli sec)=0 nextExpiration=null timerState=IN_TIMEOUT info=EjbTimerJob [timerJobInstance=GlobalJpaTimerJobInstance [timerServiceId=evaluation_1.0.0-SNAPSHOT-timerServiceId, getJobHandle()=EjbGlobalJobHandle [uuid=6_14_START]]]]: javax.ejb.EJBException: java.lang.RuntimeException: java.lang.IllegalStateException: Runtime manager evaluation_1.0.0-SNAPSHOT is already closed
- is cloned by
-
JBPM-8363 EJB Timer error in development mode for existing process during deploy
- Resolved