There's no attachment.
On Mon, Mar 4, 2013 at 11:16 AM, <dmitry.vol...@eiskonzept.com> wrote: > 4 files are created in project root(I start tomee maven plugin here): > > "\test.db.lck" > "\test.db.log" > "\test.db.properties" > "\test.db.script" > > I have purged all this files, then restarted TomEE, scheduled a job and > stopped TomEE after a while. Please find attached test.db.log file. > > -----Ursprüngliche Nachricht----- > Von: John D. Ament [mailto:john.d.am...@gmail.com] > Gesendet: Montag, 4. März 2013 16:56 > An: users@tomee.apache.org > Betreff: Re: CalendarTimers created with TimerService and persistent=true > are not persisted over tomee restart > > Yes, that file. Where does it end up getting created? > > > On Mon, Mar 4, 2013 at 10:49 AM, <dmitry.vol...@eiskonzept.com> wrote: > > > Sorry, don't get your question. Which file do you mean? Test.db? > > > > -----Ursprüngliche Nachricht----- > > Von: John D. Ament [mailto:john.d.am...@gmail.com] > > Gesendet: Montag, 4. März 2013 15:17 > > An: users@tomee.apache.org > > Betreff: Re: CalendarTimers created with TimerService and > > persistent=true are not persisted over tomee restart > > > > Are you able to query that file to see the contents? What's in there > > as your application is running? > > > > > > On Mon, Mar 4, 2013 at 8:12 AM, <dmitry.vol...@eiskonzept.com> wrote: > > > > > Hi. > > > > > > CalenderTimers created with following code are not recovered after > > > TomEE restart. Are there some TomEE properties to make timers > > > persistent across restarts? > > > There is issue reproduction: https://github.com/eiskonzept/tomee.git > > > Just start tomee plugin with node1 profile, open > > > <context_path>/schedule.xhtml and push "Schedule timer" Button. > > > Timer is scheduled(executed every second, see log) and listed on the > > page. > > > Restart application, open <context_path>/schedule.xhtml again. There > > > are no scheduled timers. > > > > > > > > > Regards. > > > Dmitry Volkov. > > > > > > Timer creation: > > > @Resource > > > private TimerService timerService; > > > > > > @Override > > > @Timeout > > > public void scheduleMe() { > > > log.warn("Scheduled method executed. " + new > Date().toString()); > > > } > > > > > > @Override > > > public void schedule() { > > > ScheduleExpression schedule = new ScheduleExpression(); > > > schedule.hour("*"); > > > schedule.minute("*"); > > > schedule.second("*"); > > > timerService.createCalendarTimer(schedule, new > > > TimerConfig(null, true)); > > > } > > > > > > Quartz config: > > > org.quartz.scheduler.instanceName = myScheduler > > > org.quartz.scheduler.instanceId = instance1 > > > > > > org.quartz.scheduler.threadsInheritContextClassLoaderOfInitializer=true > > > org.quartz.scheduler.makeSchedulerThreadDaemon=true > > > org.quartz.jobStore.makeThreadsDaemons=true > > > org.quartz.jobStore.dataSource = testDS > > > org.quartz.jobStore.nonManagedTXDataSource = testDSNonJta > > > org.quartz.threadPool.threadCount = 10 > > > org.quartz.jobStore.class = > > > org.quartz.impl.jdbcjobstore.JobStoreCMT > > > org.quartz.jobStore.driverDelegateClass = > > > org.quartz.impl.jdbcjobstore.HSQLDBDelegate > > > org.quartz.jobStore.isClustered = true > > > org.quartz.jobStore.tablePrefix = QRTZ_ > > > > > > org.quartz.dataSource.testDS.jndiURL=java:/jdbc/testDS > > > > > > org.quartz.dataSource.testDSNonJta.jndiURL=java:/jdbc/testDSNonJta > > > > > > DataSource config: > > > <Resource id="jdbc/testDS" type="javax.sql.DataSource"> > > > JdbcDriver org.hsqldb.jdbcDriver > > > JdbcUrl jdbc:hsqldb:file:test.db > > > UserName sa > > > Password > > > JtaManaged true > > > ConnectionProperties > > > </Resource> > > > > > > <Resource id="jdbc/testDSNonJta" type="javax.sql.DataSource"> > > > JdbcDriver org.hsqldb.jdbcDriver > > > JdbcUrl jdbc:hsqldb:file:test.db > > > UserName sa > > > Password > > > JtaManaged false > > > ConnectionProperties > > > </Resource> > > > > > > > > > > > >
