Hi!
We are using the TomEE 1.6.0 snapshot from yesterday.
We have scheduled beans (e.g. JobSchedulerBean) that handle persistent
timers.
While server is starting (and a timeout happened while server was down) the
ejbTimeout happens before according scheduler bean is registered and the
trigger gets lost.
Following log message appears:
26.07.2013 09:56:54 org.apache.openejb.core.timer.EjbTimerServiceImpl
ejbTimeout
WARNUNG: Exception from ejbTimeout on JobSchedulerBean
org.apache.openejb.OpenEJBException: Deployment does not exist in this
container. Deployment(id='JobSchedulerBean'), Container(id='Default
Singleton Container')
at
org.apache.openejb.core.singleton.SingletonContainer.invoke(SingletonContainer.java:156)
at
org.apache.openejb.core.timer.EjbTimerServiceImpl.ejbTimeout(EjbTimerServiceImpl.java:734)
at
org.apache.openejb.core.timer.EjbTimeoutJob.execute(EjbTimeoutJob.java:39)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
Followed by:
26.07.2013 09:56:54 org.apache.openejb.core.timer.EjbTimerServiceImpl
ejbTimeout
WARNUNG: Failed to execute ejbTimeout on JobSchedulerBean successfully
within 1 attempts
Later the EJB is started:
26.07.2013 09:56:54 org.apache.openejb.assembler.classic.Assembler startEjbs
INFO: Created Ejb(deployment-id=JobSchedulerBean, ejb-name=JobSchedulerBean,
container=Default Singleton Container)
Is there a way to get the scheduling started after all ejbs are started?
Best regards,
Thomas
--
View this message in context:
http://openejb.979440.n4.nabble.com/EjbTimeout-before-scheduler-bean-available-tp4664366.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
