Hi first can be related to column format/size.
second is related to driver I think. This parameter can be not supported (that's why we removed it by default in our db pool - before it was set for each db pool) *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/10/22 tschuler <[email protected]> > Hi Romain! > > I was able to get the scheduled beans running with oracle database > persisting. > > First approach was to deactivate oracle optimization handling disk space > for > empty tables (DEFERRED_SEGMENT_CREATION). > This fixes the problem only partially - tomee startup was successful but > adding cron timers failed unpredictable (showing the same oracle error > ORA-08177). > > Second approach was successful: > In application.properties (describing the quartz persistence) the > org.quartz.jobStore.txIsolationLevelSerializable must be set to false. > Tomee > startup is successful, scheduled beans are handled as expected. > > Do you have an idea, why: > - in the first approach - adding the cron timers sometimes failed? > - in the second approach - txIsolationLevelSerializable cannot be set to > true in case of an oracle database? > > 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-tp4665596p4665698.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
