Don't forget that JBoss runs it's own instance of Quartz as a service. I'm not sure how you're configuring the JobStore implementation, but if it's via the quartz.properties and the JBoss instance of quartz reads the same properties, then maybe there's a conflict?
On Mon, May 20, 2013 at 5:41 PM, mpaivafontes <mpaivafon...@gmail.com> wrote: > Hello, > > I'm trying to use the misfire property from Camel-Quartz persisting the data > at the database ( SQL server ) with JobStore from Quartz but i'm facing a > strange problem after the restart of the application. > > For some reason after the restart, all data disappear for some reason and > the misfire is not getting triggered. > > When i setted the xx.isClustered=true the all data is kept what does make > sense, but it's not my case. > > I would like to know if is there any way to keep the data intact after the > app restart so i can see the misfire working properly. > > The class used to control the transaction is > org.quartz.impl.jdbcjobstore.JobStoreTX > > Regards ! > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Quartz-and-JobStore-tp5732853.html > Sent from the Camel - Users mailing list archive at Nabble.com.
