should be fine now was an error (two attributes were not reinitialized correctly) in the serialization of TimerData + EJBCronExpression *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 tschuler > Hi Romain! > > I added a small test suite checking some scheduler bean basics: > > - SchedulerBeanUnderTest.java: Is the scheduler bean used for the > tests > > - SchedulerBeanBasics.java: Includes the six tests called from > the following two real test classes > > - CheckInMemorySchedulerBeanBasicsTest.java: Test class for > testing an in memory scheduler bean (no quartz persistence) > > - CheckPersistedSchedulerBeanBasicsTest.java: Test class for > testing a persisted scheduler bean (quartz persistence in hsqldb) > The tests run on the actual TomEE 1.6.0 snapshot (including quartz 2.2.0), > but usage of former snapshots is possible (simply set IS_QUARTZ_2_2_0 in > CheckPersistedSchedulerBeanBasicsTest to false). > > What can be seen is that > CheckPersistedSchedulerBeanBasicsTest.testCronTimer() fails: This is the > error I described within this topic. > If you use an older TomEE 1.6.0 snapshot (e.g. the one from 5th august) > the test runs as expected - therefore a change done in the meanwhile causes > the issue. > Can you please have a deeper look inside the cause? > > Best regards, > Thomas > > > > > SchedulerBeanBasicTests.zip (7K) < > http://openejb.979440.n4.nabble.com/attachment/4664982/0/SchedulerBeanBasicTests.zip > > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Fired-cron-trigger-not-available-tp4664936p4664982.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >