Catch Errors in Windows Service
I've been thrown into a remoting production issue and am looking for some
insight as I have never done remoting before.
There is a Windows Service that creates a TcpChannel and everything works
fine for some undeterminate amount of time and then it would appear as the
channel just stops handling requests. The service is still up and running
and we see ** NO ** indication in the event logs that indicate a restart had
occurred.
So if the port did shut down, is there some kind of notification? Is there
a way to determine if the port shut down or stopped accepting messages?
Would a AppDomain.CurrentDomain.UnhandledException be helpful to implement?
As a final note, the code is running .NET v1.1.
Any thoughts are greatly appreciated.
Dave
Date:Mon, 20 Aug 2007 06:24:02 -0700
Author:
|