[Rets-dev] Timeout exception

[Dan Woolley]

We do not have any timeout or drop connection issues with our .NET RETS
classes and we are running them in .NET 2003 (1.1 Framework).  I notice
we have explicit code to both close and set to Nothing all these objects
after *each* communication with the server:  request, response,
streamreader, and any xmlreader (if used).  Closing and setting them to
nothing seems a little over-kill, but it was put in there three years
ago for some reason, and it could have been due to the same problem you
are seeing.

I also see we are setting the request.keepalive to True and explicitly
setting the request.timeout to a value between 30 and 60 seconds.


Dan Woolley
Vice President of Technology
www.eneighborhoods.com


-----Original Message-----
From: rets-dev-bounces at rets.org [mailto:rets-dev-bounces at rets.org] On
Behalf Of Sanja Tanasijevic
Sent: Friday, March 17, 2006 8:43 AM
To: rets-dev at rets.org
Subject: [Rets-dev] Timeout exception

Hi!


I developed RETS Client in Visual Studio 2005. It worked good. When I
transfered it in VS 2003. It started failing. Timeout exception is
constant problem. Almost after every single transaction I have to
restart application, even more times. Otherwise, it's going on
indefinetly until it  break on Time out exception.
I am closing all streams and response. But it doesn't help  at all.
Any solution to this problem?




 


		
___________________________________________________________
Yahoo! Photos - NEW, now offering a quality print service from just 8p a
photo http://uk.photos.yahoo.com
_______________________________________________
Rets-dev mailing list
Rets-dev at rets.org
http://lists.rets.org/mailman/listinfo/rets-dev
*** eSafe scanned this email for malicious content ***
*** IMPORTANT: Do not open attachments from unrecognized senders  ***