 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / New Users / August 2005Recover after HttpWebResponse error
We have a problem getting the response from one particular webpage (I am not allowed to give it away). The problem is that sometimes it fails (unexpected termination by server) and then all subsequent calls to that page will also fail. However, restarting the application very often solves the problem. Calls to other URL's is not affected, they are always succesful, even after a failure to get the page mentioned above. The page does not use any kind of cookies. Is there a way to totally reset the net handling infrastructure in .Net in order to get the same result without restarting the application? We want to implement retries after failure, but then we have to be able to "simulate" an application restart. /Patrik > We have a problem getting the response from one particular webpage (I > am not allowed to give it away). [quoted text clipped - 11 lines] > application? We want to implement retries after failure, but then we > have to be able to "simulate" an application restart. I'm not aware of any "reset" like feature. What problem exactly causes this failure? Cheers,  Signaturehttp://www.joergjooss.de mailto:news-reply@joergjooss.de > I'm not aware of any "reset" like feature. What problem exactly causes > this failure? Sometimes we just get an "unexpected termination by the server". I guess it is caused by the server not beeing very reliable, and that wouldn't be a problem if we were able to just retry. But we are not since all subsequent calls will fail. From another computer though (or the same computer after the application has been terminated and restarted) it is no problem. The same problem occurs when surfing to the page with IE. Once you get the error all instances of IE must be closed. Then you can once again reach the page. My only conclussion is that it is some low level routines in dotnet that must be reinitialized. /Patrik > > I'm not aware of any "reset" like feature. What problem exactly > > causes this failure? > > Sometimes we just get an "unexpected termination by the server". I > guess it is caused by the server not beeing very reliable, and that > wouldn't be a problem if we were able to just retry. It would be interesting to know what happens on the server-side in this situation. It is an application level error or a server error? > But we are not since all subsequent calls will fail. From another > computer though (or the same computer after the application has been [quoted text clipped - 4 lines] > again reach the page. My only conclussion is that it is some low > level routines in dotnet that must be reinitialized. Is your system up-to-date? I've run across more IE goof-ups than what could be considered healthy for one human being, but never something like you've described :-S Cheers, Signaturehttp://www.joergjooss.de mailto:news-reply@joergjooss.de
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.