Hard coded timer in Generic Agent for OTRS 2.0.4
Hi, We noticed a strange behaviour with our GenericEgent scheduled task if they were to use a 10 minutes interval : we found in the GenericAgent.pl file some hard-coded « timer » equal to 10 minutes that would explain this : should a task be re-executed about 9m59secs later (because of system latency at the former run), OTRS would declare it already finished". if ($DBJobRaw{ScheduleLastRunUnixTime} && $CurrentTime < $DBJobRaw{ScheduleLastRunUnixTime}+(10*60)) We fiwed it by changing the timer to 5 minutes (5*60), but as we found no notes of this control feature in the documentation I send you this. I dont know if its fixed in the current release, but I warn just in case. Regards, Laurent Hiesse
Hi Laurent, Laurent Hiesse schrieb:
We noticed a strange behaviour with our GenericEgent scheduled task if they were to use a 10 minutes interval : we found in the GenericAgent.pl file some hard-coded « timer » equal to 10 minutes that would explain this : should a task be re-executed about 9m59secs later (because of system latency at the former run), OTRS would declare it “already finished".
if ($DBJobRaw{ScheduleLastRunUnixTime} && $CurrentTime < $DBJobRaw{ScheduleLastRunUnixTime}+(10*60))
We fiwed it by changing the timer to 5 minutes (5*60), but as we found no notes of this control feature in the documentation I send you this.
I don’t know if it’s fixed in the current release, but I warn just in case.
Yes, it's true, the min. interval is currently 10 minutes. So 5 minutes are currently not implemented.
Laurent Hiesse
Greetings, Martin Edenhofer ((otrs)) :: OTRS GmbH :: Europaring 4 :: D - 94315 Straubing Fon: +49 (0) 9421 1862 760 :: Fax: +49 (0) 9421 1862 769 http://www.otrs.com/ :: Communication with success!
participants (2)
-
Laurent Hiesse -
Martin Edenhofer