System.Threadin g.Timer fires too quickly!

[Kenny]

I am running a windows service that takes actions based on a couple
System.Threadin g.Timers. The intervals are usually short... based on
the time of day, anywhere between 1 and 5 minutes. Recently however,
the event that was firing based on the timer started firing rapidly; it
fired about 9000 times in a minute and a half. After the minute and a
half was up, it returned to normal behavior!

.... just wondering if anyone has experienced this strange behavior and
if they've found a solution. There was another posting on this a few
months ago, but there were no responses
(http://groups-beta.google.com/group/...5803fd38be2abe)

Much thanks for any help!

[Hans Kesting]

Kenny wrote:

I am running a windows service that takes actions based on a couple
System.Threadin g.Timers. The intervals are usually short... based on
the time of day, anywhere between 1 and 5 minutes. Recently however,
the event that was firing based on the timer started firing rapidly; it
fired about 9000 times in a minute and a half. After the minute and a
half was up, it returned to normal behavior!

... just wondering if anyone has experienced this strange behavior and
if they've found a solution. There was another posting on this a few
months ago, but there were no responses
(http://groups-beta.google.com/group/...5803fd38be2abe)

Much thanks for any help!

"based on time of day", could it be that there are specific times
that are between the "usual" periods that end up with an interval
of 1/100 seconds? Say "time < 08:00" = 5 minutes,
"time > 08:00" = 1 minutes, then what about 08:00 itself?
How exactly are you calculating that interval?

--
Hans Kesting

[Kenny]

I have a loop that does some work. In my config file, I specify a
value "peak hours". At the top of the loop, I check to see what time
it is. If I am within the peak hours, my interval is 1 minute,
otherwise it is 5 minutes. I set the timer with one of those values.
The body of the loop does some work, and at the bottom of the loop, I
wait for an AutoResetEvent that is set by the callback of the Timer.

I've debugged the code and it just doesn't seem possible for the
interval to have a value other than 1 or 5 because I'm using an if-else
to set the interval value. If it's within peak hours, set it to 1,
else 5.

Here is the main bit of the code...
public void StartMessages(o bject state)
{
int timeBetweenRequ ests;
Timer requestTimer;
AutoResetEvent[] events = new AutoResetEvent[2];

while( true )
{
timeBetweenRequ ests = GetRequestInter val();

for(int i = 0; i < m_Requestors.Co unt;)
{
RequestorData rd = (RequestorData) m_Requestors[i];

requestTimer = new Timer(new TimerCallback(t his.SignalNextR equest),
m_SendNextReque st,
timeBetweenRequ ests, Timeout.Infinit e);

try
{
if(rd.Type == RequestorType.D ialUp)
{
DoDialUpRequest (rd);
}
else if(rd.Type == RequestorType.N etwork)
{
DoNetworkReques t(rd);
}
else
{
throw new V1ErrorExceptio n(ErrorInfo.Inv alidRequestorTy pe);
}
}
catch(V1ErrorEx ception v1Err)
{
ExceptionManage r.Publish(v1Err );
}

events[0] = m_SendNextReque st;
events[1] = m_EndRequestLoo p;

int eventIndex = WaitHandle.Wait Any(events);
requestTimer.Di spose();

if(eventIndex != 0)
{
Debug.WriteLine ("Signal received to kill request group. Ending
request loop.");
return;
}
}
}
}

private int GetRequestInter val()
{
DateTime now = new DateTime(DateTi me.Now.Ticks);
int currentTime = now.Hour * 100 + now.Minute;

if( currentTime >=
Convert.ToInt32 (MonitorConfigR eader.MonitorSe ttings("peakHou rsStart"),
CultureInfo.Inv ariantCulture) &&
currentTime <=
Convert.ToInt32 (MonitorConfigR eader.MonitorSe ttings("peakHou rsEnd"),
CultureInfo.Inv ariantCulture) )
{
return
Convert.ToInt32 (MonitorConfigR eader.MonitorSe ttings("peakHou rsRequestInterv al"),
CultureInfo.Inv ariantCulture);
}
else
return
Convert.ToInt32 (MonitorConfigR eader.MonitorSe ttings("offPeak HoursRequestInt erval"),
CultureInfo.Inv ariantCulture);
}

[Deiussum]

Kenny wrote:

I have a loop that does some work. In my config file, I specify a
value "peak hours". At the top of the loop, I check to see what time
it is. If I am within the peak hours, my interval is 1 minute,
otherwise it is 5 minutes. I set the timer with one of those values.
The body of the loop does some work, and at the bottom of the loop, I
wait for an AutoResetEvent that is set by the callback of the Timer.

I've been running into a similar situation. For me it has only been on
setting a very long dueTime > 8 days or so. Instead of waiting that
amount of time, it fires immediately.

I tried to narrow it down, to a specific dueTime, but it seemed that as
the system time progressed, the dueTime that started to demonstrate this
problem decreased. Currently, it seems that if I try to set a dueTime
that will expire after a fluctuating time on 2005-04-07 it demonstrates
this behavior. And the time seems to be getting slowly earlier...

I'm curious what will happen as that date gets closer. Will it fire
right away with a dueTime as low as 1 minute then? After that point in
time, what date will start giving this problem? It definitely seems
like some sort of bug to me, though what they could have done to
demonstrate this odd behavior is beyond me.