Hi! We are using latest TomEE 1.6.0 snapshot and try to persist scheduled beans in an oracle database. The TomEE startup fails because the default scheduler cannot be initialized.
Attached zip ( DefaultSchedulerInitializeError.zip <http://openejb.979440.n4.nabble.com/file/n4665596/DefaultSchedulerInitializeError.zip> ) includes the error message and simple tests for scheduler initializations: - PersistedSchedulerBeanOracleTest.java: demonstrates failed startup for oracle database - PersistedSchedulerBeanMSSQLTest.java: demonstrates successful startup for mssql database - SchedulerBeanUnderTest.java: (needed as @Module and for further tests) - DefaultSchedulerInitializeError.txt: Server startup exception while default scheduler initialization To make the tests running an oracle/mssql database and an oracle/mssql jdbc driver (ojdbc6.jar/sqljdbc4.jar) are needed, also URL, USERNAME and PASSWORD in Testclasses must be adapted. The test creates the needed quartz tables while startup and deletes them while shutdown. A simple test case (that does nothing right now) enforces the server startup. Can you give a hint why default scheduler cannot be initialized while server startup? Best regards, Thomas -- View this message in context: http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596.html Sent from the OpenEJB User mailing list archive at Nabble.com.
