Hmm, wonder if it was not an issue of 1.6 then, did you try on 1.7?
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-03-30 22:04 GMT+02:00 Leonardo K. Shikida <[email protected]>: > Hi Romain > > it's already a @Singleton with @Lock(Read) > > but timers are persistent and tomee is 1.6.0 > > [] > > Leo > > On Mon, Mar 30, 2015 at 4:55 PM, Romain Manni-Bucau <[email protected] > > > wrote: > > > Hi > > > > is it a @Singleton? If yes add @Lock(READ) > > > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <http://rmannibucau.wordpress.com> | Github < > > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > > <http://www.tomitribe.com> > > > > 2015-03-30 21:32 GMT+02:00 Leonardo K. Shikida <[email protected]>: > > > > > Hi > > > > > > I have a timer like this > > > > > > @Schedule(second = "0", minute = "*", hour = "*", info = > > > "myperiodicjob") > > > public void myPeriodicJob() { > > > } > > > > > > sometimes this method can hang, and then subsequent executions are > > blocked > > > until the previous running one finishes. > > > > > > is there any way to change this behaviour? allowing other executions to > > > happen even if the previous ones are not completed? > > > > > > TIA > > > > > > Leo > > > > > >
