Not getting anything back is not a problem which is why I wanted to use OneWay.
Unfortunately no exception is thrown if the target is not available - at least none that I can get access to. Its probably caught inside the remoting infrastructure but not dealt with properly hence the memory retention and handle count increase. I simply removed the [OneWay] attribute and all works fine now. One blip is that if a target becomes unavailable then it can be up to 30 seconds before the exception is thrown but during that period, messages are still added into the queue and once the offending clients connection is removed then the remaining clients get a stream of backed up messages. Still its better than having the service crash with out of memory and disorderly client disconnects will be rare anyway. Cheers Simon -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Ben Kloosterman Sent: 02 June 2005 02:53 To: [email protected] Subject: Re: [ADVANCED-DOTNET] Remoting, OneWay and memory/handle leak problem > As I understand it, a proxy created by the remoting infrastructure uses > a threadpool thread to communicate with the remote client, sees that the > method in OneWay and doesn't wait for a reply. > All this works fine when the client can be reached but if it can't then > my guess is that some exception is caught internally but the handler is > not cleaning up properly and holding onto references and/or handles. If it does not finds the server you will probably get a net exception within a method invoke exception . The issue I found was if the server is busy, times out, has a problem or a validation error you get nothing back. Hence I rarely use Oneway . Ben =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
