tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: Cluster + @Schedule
Date Sat, 18 Oct 2014 13:23:10 GMT
Le 18 oct. 2014 14:47, "Leonardo K. Shikida" <shikida@gmail.com> a écrit :
>
> > "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?
>

If that s the same for the same bean with same data it doesnt shock me. If
not persistence adapter id maybe needs some tweak

> 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