dotnet remoting: 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.

How did you register your remote object(s)?

I recall that when I first got started with remoting, I had a similar
problem with my singleton remote objects - they do have a lifetime by
default, and if there's no activity on them, the timeout elapses and the
object will be garbage collected.

Could that be the reason for your troubles?

Regards
Stephan