Hi, yes it's the same database.
Well, you're probably right. I moved my scheduling completely over to use quartz configuration/initializing and I get the failover/persistency I need for clustering. BTW, I've read that the application.properties including quartz properties is supposed to be put in WEB-INF (for war). I was actually hoping I could use StdSchedulerFactory.getDefaultScheduler() but this always returns default RAMJobStore so I have to initialize factory with props. Again, is this how it's supposed to be? br, hw -- View this message in context: http://openejb.979440.n4.nabble.com/TomEE-and-persistent-timers-tp4666750p4666754.html Sent from the OpenEJB User mailing list archive at Nabble.com.
