Ken Kolda
8/13/2004 4:05:00 PM
A couple of questions:
1) Does your server hold any references to remoted objects from the clients
(e.g. event delegates)? One possibility I can think of is that, for example,
if you have a server event to which your clients have subscribed and a
client dies, then you'll run into problems when the server next raises the
event.
2) Do you override InitializeLifetimeService() on your SAO or otherwise do
something to ensure its lease doesn't expire? The client disconnect thing
may be a red herring -- it may just be your server object is expiring (or,
it could be the client is crashing because it's attempting to access the
expired server object).
If neither of those is the case, what are the symptoms you're experiencing,
i.e. what happens in your other clients when you next attempt to invoke the
SAO? And what is the exception you get when you attempt to restart your
client app? Lastly, is your SAO a singleton or single-call and are you
remoting it by calling RemotingServices.Marshal() or using
RegisterWellKnownServerType()?
Ken
"k a" <le_khan@yahoo.fr> wrote in message
news:8f1b5e2a.0408130221.ddae730@posting.google.com...
> Hi NG
>
> I'm using .net remoting in my server / clients app.
> It works quite well.
> But...
>
>
> When a client crashes (still some bugs in my code...), the connection
> is lost for the other clients too.
> I mean that some remote objects on the server are not available
> anymore
> I don't understand how a client crash can affect the SAO.
>
> That's a pb, because when I try to restart the client, the remote
> connection fails.
> I have to restart the server app and then restart the client app.
>
> Have anyone encounter this before?
> Thanks for your help
>
> ka