|
|
You're in the
dotnet remoting
group:how to implement pinging
dotnet remoting:
I have a long running remoting client that every once in a while calls
a method on a remoting server. The client constantly displays the connection status. How can the remoting client find out that the remoting server has become unavailable right after it happend? Does .NET Remoting have any built in ping-like functionality? What is the best practice in .NET Remoting for (keep) alive probing?
"Robert Ludig" <schwertfischtrombose@gmx.de> wrote in
news:1176277585.267836.321700@n59g2000hsh.googlegroups.com: [quoted text, click to view] > I have a long running remoting client that every once in a while calls > a method on a remoting server. The client constantly displays the > connection status. How can the remoting client find out that the > remoting server has become unavailable right after it happend? > Does .NET Remoting have any built in ping-like functionality? What is > the best practice in .NET Remoting for (keep) alive probing? Unfortunately no - not in the default channels. You'll need something like Geniune Channels. However, with the built in channels, just create a timer and fire off a function call to a dummy function on the server. If the function times out
[quoted text, click to view]
On Apr 11, 8:59 pm, Spam Catcher <spamhoney...@rogers.com> wrote: > "Robert Ludig" <schwertfischtromb...@gmx.de> wrote innews:1176277585.267836.321700@n59g2000hsh.googlegroups.com: > > > I have a long running remoting client that every once in a while calls > > a method on a remoting server. The client constantly displays the > > connection status. How can the remoting client find out that the > > remoting server has become unavailable right after it happend? > > Does .NET Remoting have any built in ping-like functionality? What is > > the best practice in .NET Remoting for (keep) alive probing? > > Unfortunately no - not in the default channels. > > You'll need something like Geniune Channels. > > However, with the built in channels, just create a timer and fire off a > function call to a dummy function on the server. If the function times out > (or errors), you know your connection is fubar. There is only one problem with you suggested approach: How do I control the timeout? When I call the remote server that is not reachable the application hangs for a long time. (I haven't figured out yet where that timespan comes from.) Not only do I want my app to not hang but also I would like to specify my own timeout timespan. I could of course call the ping in a dedicated thread and kill that thread if it does not return for a specified timespan but one thread for each ping and each remoting client? That'd be a hell of a lot threads.
"Robert Ludig" <schwertfischtrombose@gmx.de> wrote in
news:1176357364.698091.170770@y5g2000hsa.googlegroups.com: [quoted text, click to view] > On Apr 11, 8:59 pm, Spam Catcher <spamhoney...@rogers.com> wrote: >> "Robert Ludig" <schwertfischtromb...@gmx.de> wrote >> innews:1176277585.267836.321700@n59g2000hsh.googlegroups.com: >> >> > I have a long running remoting client that every once in a while >> > calls a method on a remoting server. The client constantly displays >> > the connection status. How can the remoting client find out that >> > the remoting server has become unavailable right after it happend? >> > Does .NET Remoting have any built in ping-like functionality? What >> > is the best practice in .NET Remoting for (keep) alive probing? >> >> Unfortunately no - not in the default channels. >> >> You'll need something like Geniune Channels. >> >> However, with the built in channels, just create a timer and fire off >> a function call to a dummy function on the server. If the function >> times out (or errors), you know your connection is fubar. > > There is only one problem with you suggested approach: > How do I control the timeout? When I call the remote server that is > not reachable the application hangs for a long time. Run the ping in a separate thread so it does not lock up your GUI thread. [quoted text, click to view] > (I haven't > figured out yet where that timespan comes from.) Not only do I want my > app to not hang but also I would like to specify my own timeout > timespan. I think you can specify the timeout on certain .NET channels during the setup. Check the configuration parameters ... [quoted text, click to view] > I could of course call the ping in a dedicated thread and > kill that thread if it does not return for a specified timespan but > one thread for each ping and each remoting client? That'd be a hell of > a lot threads. You don't need to create multiple ping threads. Just have each client ping the server with 1 thread (and reuse the thread). The server
[quoted text, click to view]
On Apr 12, 8:59 pm, Spam Catcher <spamhoney...@rogers.com> wrote: > "Robert Ludig" <schwertfischtromb...@gmx.de> wrote innews:1176357364.698091.170770@y5g2000hsa.googlegroups.com: > > > > > > > On Apr 11, 8:59 pm, Spam Catcher <spamhoney...@rogers.com> wrote: > >> "Robert Ludig" <schwertfischtromb...@gmx.de> wrote > >> innews:1176277585.267836.321700@n59g2000hsh.googlegroups.com: > > >> > I have a long running remoting client that every once in a while > >> > calls a method on a remoting server. The client constantly displays > >> > the connection status. How can the remoting client find out that > >> > the remoting server has become unavailable right after it happend? > >> > Does .NET Remoting have any built in ping-like functionality? What > >> > is the best practice in .NET Remoting for (keep) alive probing? > > >> Unfortunately no - not in the default channels. > > >> You'll need something like Geniune Channels. > > >> However, with the built in channels, just create a timer and fire off > >> a function call to a dummy function on the server. If the function > >> times out (or errors), you know your connection is fubar. > > > There is only one problem with you suggested approach: > > How do I control the timeout? When I call the remote server that is > > not reachable the application hangs for a long time. > > Run the ping in a separate thread so it does not lock up your GUI > thread. > > > (I haven't > > figured out yet where that timespan comes from.) Not only do I want my > > app to not hang but also I would like to specify my own timeout > > timespan. > > I think you can specify the timeout on certain .NET channels during the > setup. Check the configuration parameters ... Yes I have tried that. But those timouts do not seem have any effect in case the server is not reachable. This is how I did it: Hashtable properties = new Hashtable(); properties.Add("port", 0); // let system pick an open port properties.Add("timeout", 10000); // 10 second timeout... IClientChannelSinkProvider provider = new BinaryClientFormatterSinkProvider(); provider.Next = new CompressedClientChannelSinkProvider(); HttpChannel channel = new HttpChannel(properties, provider, null); channel.WantsToListen = false; ChannelServices.RegisterChannel(channel); Anything wrong with that? [quoted text, click to view] > > > I could of course call the ping in a dedicated thread and > > kill that thread if it does not return for a specified timespan but > > one thread for each ping and each remoting client? That'd be a hell of > > a lot threads. > > You don't need to create multiple ping threads. Just have each client > ping the server with 1 thread (and reuse the thread). The server > responds to the ping with some dummy data.- Hide quoted text - > > - Show quoted text -
More recent OS versions have the WMI Win32_PingStatus class that you can
call using the Management classes. There are some C# implementations out there, like this one: http://www.codeproject.com/dotnet/CSharpPing.asp -- Phil Wilson [Microsoft MVP-Windows Installer] [quoted text, click to view] "Spam Catcher" <spamhoneypot@rogers.com> wrote in message news:Xns990F9867EBC4Cusenethoneypotrogers@127.0.0.1... > "Robert Ludig" <schwertfischtrombose@gmx.de> wrote in > news:1176277585.267836.321700@n59g2000hsh.googlegroups.com: > >> I have a long running remoting client that every once in a while calls >> a method on a remoting server. The client constantly displays the >> connection status. How can the remoting client find out that the >> remoting server has become unavailable right after it happend? >> Does .NET Remoting have any built in ping-like functionality? What is >> the best practice in .NET Remoting for (keep) alive probing? > > Unfortunately no - not in the default channels. > > You'll need something like Geniune Channels. > > However, with the built in channels, just create a timer and fire off a > function call to a dummy function on the server. If the function times out > (or errors), you know your connection is fubar.
This not an option because it doen't ping the actual remoting objects.
There is no way to guarantee that the remote object is available. While the host (aka the remote machine) might be pingable that doesn't mean that the remoting server on a specifc port and remoting uri is available on that machine. Also if you wanted pinging the way you described there is no need to use wmi. You can simply use the ping class of the .NET Framework: http://msdn2.microsoft.com/en-us/library/system.net.networkinformation.ping.aspx [quoted text, click to view] On 20 Apr., 05:30, "Phil Wilson" <pdjwil...@nospam.cox.net> wrote: > More recent OS versions have the WMI Win32_PingStatus class that you can > call using the Management classes. > > There are some C# implementations out there, like this one: > > http://www.codeproject.com/dotnet/CSharpPing.asp > > -- > Phil Wilson > [Microsoft MVP-Windows Installer] > > "Spam Catcher" <spamhoney...@rogers.com> wrote in message > > news:Xns990F9867EBC4Cusenethoneypotrogers@127.0.0.1... > > > > > "Robert Ludig" <schwertfischtromb...@gmx.de> wrote in > >news:1176277585.267836.321700@n59g2000hsh.googlegroups.com: > > >> I have a long running remoting client that every once in a while calls > >> a method on a remoting server. The client constantly displays the > >> connection status. How can the remoting client find out that the > >> remoting server has become unavailable right after it happend? > >> Does .NET Remoting have any built in ping-like functionality? What is > >> the best practice in .NET Remoting for (keep) alive probing? > > > Unfortunately no - not in the default channels. > > > You'll need something like Geniune Channels. > > > However, with the built in channels, just create a timer and fire off a > > function call to a dummy function on the server. If the function times out > > (or errors), you know your connection is fubar.- Zitierten Text ausblenden - > > - Zitierten Text anzeigen -
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |