tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tschuler <>
Subject AW: AW: Fired cron trigger not available
Date Mon, 02 Sep 2013 15:00:33 GMT
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,

Von: Romain Manni-Bucau [via OpenEJB] []
Gesendet: Montag, 2. September 2013 16:55
An: Thomas Schuler
Betreff: Re: AW: Fired cron trigger not available


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 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:
> Sent from the OpenEJB User mailing list archive at

If you reply to this email, your message will be added to the discussion below:
To unsubscribe from Fired cron trigger not available, click here<>.

View this message in context:
Sent from the OpenEJB User mailing list archive at
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message