all groups > dotnet remoting > may 2006 >
You're in the

dotnet remoting

group:

Remoting - Strange Behaviour


Remoting - Strange Behaviour nikunjdhawan NO[at]SPAM gmail.com
5/23/2006 12:08:49 AM
dotnet remoting:
Hi Techies,

I am facing a strange problem while working with .Net Remoting.

I have a remoting windows service which is running on 8888 port on my
Windows XP development machine.

I have a ASP.Net application that uses this remote component.

Both of the above application are on same machine.

Everything works fine, but suddenly, after some random amount of time,
(24-36 hrs), I start getting this exception

"System.Net.Sockets.SocketException: No connection could be made
because the target machine actively refused it"

Once I restart my windows service, everything starts working like
charm.

Any help in this regard will be highly appreciated.

Regards,
Nik
Re: Remoting - Strange Behaviour liuqian
5/25/2006 10:09:10 PM
I think it's a lifetime problem.

So suggest you override "MarshalByRefObject.InitializeLifetimeService"
Method.

e.g.:

public override object InitializeLifetimeService()
{
return null;
}
Re: Remoting - Strange Behaviour Pravin
6/7/2006 12:43:02 AM
I am also getting the same problem in intervals of every 21 to 24 hrs and
restarting the service will do the magic.

I already have the overrided InitializeLifetimeService code you mentioned.
Still i am getting the same problem. Can anyone help me on this?

Thanks in Advance!


[quoted text, click to view]
AddThis Social Bookmark Button