Lock problems with System.Timers.T imer

[Ben]

Hello everybody

I got confused by this problem for which I don't have a logical explanation.
There is a Thread (ThreadA) which receives Events from another system thread
(ThreadS). ThreadA then adds a time stamp to the received event and adds it
to a event queue. This works well (therfore not shown here). The queue fills
up.
Then I used a timer to check every millisecond for new events in the queue
and send it to another thread (ThreadC). I included a lock statement on a
static object to ensure a critical section. But after some time (6 hours)
the timer stops.
I debugged it and found that i could even not restart the timer executing
m_EventTimer.St art().

What do I wrong? Why is the timer blocking?
Ok, perhaps, many events will be generated during the time the Timer_Elapsed
event happens. But the lock statement should do the job and not allow any
false Start() Stop() of the timer... What happens to the timer events which
have to wait? Does this anybody know?

Many thanks for tips
Ben

private void OnEventTimer_El apsed(object sender,
System.Timers.E lapsedEventArgs e)
{
lock(m_EventTim erLockObject)
{
MyClass.persona lMessage tmpPersMsg;
try
{
m_EventTimer.St op();
//send all events which already occurred to the TAPI class for logging
while(m_Events. Count > 0)
{
lock(m_Events)
{
tmpPersMsg= (MyClass.person alMessage )m_Events[0];
m_Events.Remove At(0);
}
this.OnLineMess age(new PersonalMessage EventArgs(tmpPe rsMsg));
}
}
catch(Exception ex)
{
Logging.LogData base(150103, ex.Message, ex.StackTrace,
LogSeverityDB.E rror, "PM.cs"); // Event timer raised an exception.
}
finally
{
m_EventTimer.St art();
}
}
}
Alternative (right now in test):
private void OnEventTimer_El apsed(object sender,
System.Timers.E lapsedEventArgs e)
{
if(System.Threa ding.Monitor.Tr yEnter(m_EventT imerLockObject) )
{
MyClass.persona lMessage tmpPersMsg;
try
{
m_EventTimer.St op();
//send all events which already occurred to the TAPI class for logging
while(m_Events. Count > 0)
{
lock(m_Events)
{
tmpPersMsg= (MyClass.person alMessage )m_Events[0];
m_Events.Remove At(0);
}
this.OnLineMess age(new PersonalMessage EventArgs(tmpPe rsMsg));
}
}
catch(Exception ex)
{
Logging.LogData base(150103, ex.Message, ex.StackTrace,
LogSeverityDB.E rror, "PM.cs"); // Event timer raised an exception.
}
finally
{
System.Threadin g.Monitor.Exit( m_EventTimerLoc kObject);
m_EventTimer.St art();
}
}
}

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,
"Ben" <Po************ @kjkjkjkjkjkjkj kjkjkjkjkjkjkjk j.com> wrote in message
news:uu******** ******@TK2MSFTN GP02.phx.gbl...

Hello everybody

I got confused by this problem for which I don't have a logical
explanation.
There is a Thread (ThreadA) which receives Events from another system
thread (ThreadS).
How you assure than the event generated in thead S is handled in thread A ?
Then I used a timer to check every millisecond for new events in the queue
and send it to another thread (ThreadC).
In what thread is this?
I included a lock statement on a static object to ensure a critical
section. But after some time (6 hours) the timer stops.
I debugged it and found that i could even not restart the timer executing
m_EventTimer.St art().

What do I wrong? Why is the timer blocking?

I'm not very sure that you need all this, first of all why you need so many
threads doing part of the process?

In addition you don't have to use lock , simply use a Syncronized queue
(Queue.Syncroni zed ). then have one thread receive the message, prepare it
and place it in the queue.

Another thread will poll the queue at a regular interval and do any process.

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

[Barry Kelly]

"Ben" <Po************ @kjkjkjkjkjkjkj kjkjkjkjkjkjkjk j.com> wrote:

I got confused by this problem for which I don't have a logical explanation.
There is a Thread (ThreadA) which receives Events from another system thread
(ThreadS). ThreadA then adds a time stamp to the received event and adds it
to a event queue. This works well (therfore not shown here). The queue fills
up.
Then I used a timer to check every millisecond for new events in the queue
and send it to another thread (ThreadC). I included a lock statement on a
static object to ensure a critical section. But after some time (6 hours)
the timer stops.
I debugged it and found that i could even not restart the timer executing
m_EventTimer.St art().

First, System.Timers.T imer is a component for UIs, you should check out
System.Threadin g.Timer for working with threading.

However, you are designing your architecture around polling - you
shouldn't do that. Google "producer consumer queue", I think you should
design your architecture in a different way.
-- Barry

[Ben]

"Ignacio Machin ( .NET/ C# MVP )" <ignacio.mach in AT dot.state.fl.us > wrote
in message news:uu******** ******@TK2MSFTN GP02.phx.gbl...

Hi,
"Ben" <Po************ @kjkjkjkjkjkjkj kjkjkjkjkjkjkjk j.com> wrote in message
news:uu******** ******@TK2MSFTN GP02.phx.gbl...

Hello everybody

I got confused by this problem for which I don't have a logical
explanation.
There is a Thread (ThreadA) which receives Events from another system
thread (ThreadS).
How you assure than the event generated in thead S is handled in thread A
?

I checked it with the debugger. Breakpoints in the event receiving method
will be hit. It works and adds events to the queue. After some time I have
several thousand events in the queue which won't be processed because the
timer stops removing them from the queue. But here is the code in ThreadA
from the loop waiting for events from ThreadS:

// Get a event
Status = WaitForSingleOb ject(m_EventHan dle, 200);
switch(Status)
{
case WaitForObjectsR esults.WAIT_OBJ ECT_0: //a event is pending,
lineMsg = new Tapi.linemessag e(0, 0, IntPtr.Zero, IntPtr.Zero,
IntPtr.Zero, IntPtr.Zero);
if (GetTapiMessage (ref lineMsg) ==
Tapi2Lib.LineEr rReturn.LINEERR _OK)
{
//Create Event
if(m_EventThrea dIsSendingLineM essages)
{
AddEvent(lineMs g);
}
}
else
{
//No Msg (LINEERR_OPERAT IONFAILED) or error
}
break;
case WaitForObjectsR esults.WAIT_TIM EOUT: //Nothing to do
break;
default: //WaitForObjectsR esults.WAIT_FAI LED,
WaitForObjectsR esults.WAIT_ABA NDONED
//TODO : GetLastError();
break;
}

private void AddEvent(MyClas s.personalMessa ge tmpPersMsg)
{
lock(m_Events)
{
m_Events.Insert (m_Events.Count , lineMsg);
}
}

Then I used a timer to check every millisecond for new events in the
queue and send it to another thread (ThreadC).
In what thread is this?

A good question. I do not know. The code is in the same class. I think the
framework creates it's own thread for timers. But I am not sure. Does it
matter? I have a static object in the class on which I apply a lock.Then I
expect the code between the {} should be handled as a critical section from
whatever thread the method will be called. Perhaps this is a false
assumption?

I included a lock statement on a static object to ensure a critical
section. But after some time (6 hours) the timer stops.
I debugged it and found that i could even not restart the timer executing
m_EventTimer.St art().

What do I wrong? Why is the timer blocking?
I'm not very sure that you need all this, first of all why you need so
many threads doing part of the process?

In addition you don't have to use lock , simply use a Syncronized queue
(Queue.Syncroni zed ). then have one thread receive the message, prepare it
and place it in the queue.

Another thread will poll the queue at a regular interval and do any
process.

I will try this. Thanks.

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

[Ben]

"Barry Kelly" <ba***********@ gmail.com> wrote in message
news:ca******** *************** *********@4ax.c om...

"Ben" <Po************ @kjkjkjkjkjkjkj kjkjkjkjkjkjkjk j.com> wrote:

I got confused by this problem for which I don't have a logical
explanation.
There is a Thread (ThreadA) which receives Events from another system
thread
(ThreadS). ThreadA then adds a time stamp to the received event and adds
it
to a event queue. This works well (therfore not shown here). The queue
fills
up.
Then I used a timer to check every millisecond for new events in the
queue
and send it to another thread (ThreadC). I included a lock statement on a
static object to ensure a critical section. But after some time (6 hours)
the timer stops.
I debugged it and found that i could even not restart the timer executing
m_EventTimer.St art().

First, System.Timers.T imer is a component for UIs, you should check out
System.Threadin g.Timer for working with threading.

However, you are designing your architecture around polling - you
shouldn't do that. Google "producer consumer queue", I think you should
design your architecture in a different way.
-- Barry

Ok I'll check the books. Thanks for the hint.