Bugzilla – Bug 5079
invalidityTime bug
Last modified: 2007-09-11 03:29:39
You need to log in before you can comment on or make changes to this bug.
Hi, I have set a trigger's invalid time last week, <trigger:TriggerRuleType> <trigger:matchingRule>//test[target/url='rls://sleepy.ccs.ornl.gov:6205' and r esult/status='DOWN']</trigger:matchingRule> <trigger:actionScript>esg-rls-ornl</trigger:actionScript> <trigger:minimumFiringInterval>86400</trigger:minimumFiringInterval> <trigger:minimumMatchTime>600</trigger:minimumMatchTime> <trigger:enableFilteredActionScriptInput>true</trigger:enableFilteredActionScr iptInput> <trigger:disableUnmodifiedActionScriptInput>true</trigger:disableUnmodifiedAct ionScriptInput> <trigger:invalidityTime> <trigger:startTime>2007-03-04T03:00:00.000Z</trigger:startTime> </trigger:invalidityTime> </trigger:TriggerRuleType> The trigger action was suppressed successfully starting on the startTime but a firing was detected on the 6th and the event was noted: RLS: rls://sleepy.ccs.ornl.gov:6205 is down -> Tue Mar 6 04:57:12 MST 2007 The rls server is now back online and so don't know if the trigger action will fire again or not. mei
This behavior should be back to normal in the developmental 4.2 trigger service. It will have to be tested, but I see no reason why this should occur in this developmental version, since the evaluations are performed in a completely different way, and virtually all the parameters are modifiable in real-time. If this anomaly still occurs in the developmental version, feel free to re-open this bug.
