Hi needs a custom timerstore I think (see https://issues.apache.org/jira/browse/TOMEE-785)
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2017-03-09 14:44 GMT+01:00 Bodo Pfelzer <bodo.pfel...@business-logics.de>: > I tried to configure persistent timers in TomEE-1.7.4 by adding: > > org.apache.openejb.quartz.jobStore.class > org.apache.openejb.quartz.impl.jdbcjobstore.JobStoreCMT > org.apache.openejb.quartz.jobStore.driverDelegateClass > org.apache.openejb.quartz.impl.jdbcjobstore.StdJDBCDelegate > org.apache.openejb.quartz.jobStore.dataSource ActiveDataSource > org.apache.openejb.quartz.jobStore.nonManagedTXDataSource > NoTxActiveDataSource > org.apache.openejb.quartz.dataSource.ActiveDataSource.jndiURL > openejb:Resource/ActiveDataSource > org.apache.openejb.quartz.dataSource.NoTxActiveDataSource.jndiURL > openejb:Resource/NoTxActiveDataSource > > to my system.properties. And yes, my EJB method annotated with @Timeout > gets called, even if TomEE was restarted during the creation of the > timer and its expiration. But two things do not work as expected: > > timerServer.getTimers() returns an empty collection after restart though > active timers exist. And perhaps even worse: Old timers get overwritten > by new ones, since MemoryTimerStore.counter always starts from zero > after restart. > > Am I missing something in my configuration? How could I replace > MemoryTimerStore? > > Best regards, > Bodo > >
