If I got it right the anser will be: retry is by execution and it stops when it passes.
Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 14:39 GMT+00:00 Lars-Fredrik Smedberg <[email protected]>: > Hi again > > Yes some of it (the vendor specific part and configuration of number of > retries / interval etc). Had forgotten about that :) > > What about the questions regarding the example? (that is if it will trigger > it twice at (almost) the same time and if the failure attempts will stop at > any successfull timer execution) > > Hope I not asked about that also before :) > > > On Thu, Nov 6, 2014 at 3:08 PM, Romain Manni-Bucau <[email protected]> > wrote: > >> Hi >> >> isn't it more or less the same as >> >> http://tomee-openejb.979440.n4.nabble.com/More-information-on-EJB-Timer-their-Exception-handling-etc-td4672037.html >> ? >> >> >> Romain Manni-Bucau >> @rmannibucau >> http://www.tomitribe.com >> http://rmannibucau.wordpress.com >> https://github.com/rmannibucau >> >> >> 2014-11-06 13:22 GMT+00:00 Lars-Fredrik Smedberg <[email protected]>: >> > Hi >> > >> > I've been looking for some details on EJB Timers and retries... maybe >> > someone can help me out on the below? >> > >> > >> > - WebSphere has default an unlimited number of retries with a 300 sec (5 >> > min) interval. >> > - Assume we have a timer that triggers every half hour and that it at >> some >> > point fails (lets assume 1 clock for the example below) >> > - Only thing I can find the EJB JSR318 EJB 3.1 is: >> > >> > - "If the container-managed transaction is rolled back, the container >> > retries the timeout." and >> > - "The container must retry the timeout after the transaction >> rollback." >> > and >> > - "If the transaction fails or is rolled back, the container must retry >> > the timeout at least once." >> > >> > Questions >> > >> > - Are all details around retries implementation specific? How does >> OpenEJB >> > handle it? >> > - Assume that the timer tasks all fail before say 1:30, will I then see >> the >> > following scenario?? >> > >> > - 1:00 - Timer due to @Schedule expression => Fails >> > - 1:05 -> 1:25 (every 5 minutes) - Timer due to retry => Fails >> > - 1:30 - Timer due to @Schedule expression => Succeed >> > - 2:00 - Timer due to @Schedule expression => Succeed >> > - ... and so on... >> > >> > - Or might the Timer trigger twice (or twice within a short timeinterval >> > around) 2:00 ? >> > - Will the retry of the Timer stop as soon as the Timer not fails >> > regardless of wether it was triggered as a result of a retry or a normal >> > @Scheduler? >> > >> > >> > >> > -- >> > Med vänlig hälsning / Best regards >> > >> > Lars-Fredrik Smedberg >> > >> > STATEMENT OF CONFIDENTIALITY: >> > The information contained in this electronic message and any >> > attachments to this message are intended for the exclusive use of the >> > address(es) and may contain confidential or privileged information. If >> > you are not the intended recipient, please notify Lars-Fredrik Smedberg >> > immediately at [email protected], and destroy all copies of this >> > message and any attachments. >> > > > > -- > Med vänlig hälsning / Best regards > > Lars-Fredrik Smedberg > > STATEMENT OF CONFIDENTIALITY: > The information contained in this electronic message and any > attachments to this message are intended for the exclusive use of the > address(es) and may contain confidential or privileged information. If > you are not the intended recipient, please notify Lars-Fredrik Smedberg > immediately at [email protected], and destroy all copies of this > message and any attachments.
