I didnt reproduced it (not enough time for it) but i fear it is related to the datastore which should be the database one in this case...which is not yet implemented as said on several jirais/threads Le 2 sept. 2013 17:02, "tschuler" <[email protected]> a écrit :
> Hi Romain! > > I know the @Schedule job was persisted failing the test. > > But what I meant with reproducing is the original error I reported: > A fired cron trigger is not available in case quartz persistence is used. > > I’ll try if I can provide a test with quartz persisted to hsqldb database. > > Best regards, > Thomas > > Von: Romain Manni-Bucau [via OpenEJB] [mailto: > [email protected]] > Gesendet: Montag, 2. September 2013 16:55 > An: Thomas Schuler > Betreff: Re: AW: Fired cron trigger not available > > Hi > > I dont have a computer right now but @Schedule was persisted and thats why > it was not working i think. > > About quartz put properties from application.properties in > ejbModule.getProperties() and return the EjbModule in the @Module method. > For the init of the db use import-[name of the datasource].sql and one > statement by line, just copy the quartz hsqldb script. Finally add a > @Configuration method returning a Properties with a datasource defined with > properties syntax. > Le 2 sept. 2013 16:37, "tschuler" <[hidden > email]</user/SendEmail.jtp?type=node&node=4664949&i=0>> a écrit : > > > Hi Romain! > > > > Can you reproduce the error I described using persisted quartz jobs? > > Can you provide me a simple example how to prepare the hsqldb for quartz > > persistence within a test and how to configure quartz for persisting in > the > > hsqldb? > > > > Best regards, > > Thomas > > > > > > > > -- > > View this message in context: > > > http://openejb.979440.n4.nabble.com/Fired-cron-trigger-not-available-tp4664936p4664948.html > > Sent from the OpenEJB User mailing list archive at Nabble.com. > > > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > > http://openejb.979440.n4.nabble.com/Fired-cron-trigger-not-available-tp4664936p4664949.html > To unsubscribe from Fired cron trigger not available, click here< > http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4664936&code=dGhvbWFzLnNjaHVsZXJAb3BlbnRleHQuY29tfDQ2NjQ5MzZ8LTE4NTIyNTQ0OTI= > >. > NAML< > http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Fired-cron-trigger-not-available-tp4664936p4664950.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
