tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tschuler <>
Subject AW: AW: AW: Fired cron trigger not available
Date Wed, 04 Sep 2013 09:51:42 GMT
Hi Romain!

I added a small test suite checking some scheduler bean basics:

- Is the scheduler bean used for the tests

- Includes the six tests called from the following two
real test classes

- Test class for testing an in memory
scheduler bean (no quartz persistence)

- 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 (7K) <>

View this message in context:
Sent from the OpenEJB User mailing list archive at
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message