tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo K. Shikida" <shik...@gmail.com>
Subject Re: Cluster + @Schedule
Date Sat, 18 Oct 2014 14:47:32 GMT
Hi José

you mean, a flag in the DB?



[]

Leo

On Sat, Oct 18, 2014 at 10:23 AM, José Luis Cetina <maxtorzito@gmail.com>
wrote:

> Hi Leo . 2 months ago I had the same problem as you (creating a quartz job
> in a cluster env) , i didnt have enough time do research about this, and
> what i finally did was creating an event (mysql event) in my database
> server (of course i Just need to modify database data) and what that my job
> was executed Just once.
>
> If this is your case (alter Just db info) Maybe you can try this to.
> El 18/10/2014 07:47, "Leonardo K. Shikida" <shikida@gmail.com> escribió:
>
> > > "hello 1413583260198" was created in a previous attempt, so my feeling
> is
> >
> > > that, somehow, even creating a new timer on every server restart, tomEE
> > (or
> > > Quartz) is assuming that the calendar timer is already created
> (checking
> > by
> > > cron expression maybe?). In fact, in the DB, there are only 3 triggers
> > > everytime.
> > > >
> > > >
> > >
> > > If persistent that s possible
> > >
> > >
> > Hi Romain
> >
> > Yeah, but then is it a bug? I mean, if I am creating a new timer, even if
> > it has the same calendar cron expression, it should not be silently
> ignored
> > just because there's already one in the DB, right?
> >
> > Yes, it's persistent. It has to be to make quartz cluster work.
> >
> > */5 no?
> > >
> > >
> > sorry, I feel so stupid about this :-)
> >
> > TIA
> >
> > Leo
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message