issues after timeout (General questions)
by Klinzter, Wednesday, May 19, 2010, 18:32 (5300 days ago)
I am having issues with the wodhttpd.dll and im doing requests to a webpage but after I get an error code #10060 when I try to do requests It starts showing errorcode #10053. the only way to make it work again is to close the app and open it again.. how can I fix this or whats wrong?
Re: issues after timeout
by wodDamir, Wednesday, May 19, 2010, 18:37 (5300 days ago) @ Klinzter
Klintzer,
The error 10060 is a Timeout error. This means that server didn't respond in the time interval specified in Timeout property.
Also, 10053 means that the connection got aborted for some reason.
Both of these issues could be caused by software installed on the machine, primarily by a Firewall. Do you have an active Firewall on that machine (Even windows firewall could cause problems)? Can you try disabling it for the test?
Regards,
Damba
Re: issues after timeout
by Klinzter, Wednesday, May 19, 2010, 18:39 (5300 days ago) @ wodDamir
Klintzer,
The error 10060 is a Timeout error. This means that server didn't respond in the time interval specified in Timeout property.
Also, 10053 means that the connection got aborted for some reason.
Both of these issues could be caused by software installed on the machine, primarily by a Firewall. Do you have an active Firewall on that machine (Even windows firewall could cause problems)? Can you try disabling it for the test?
Regards,
Damba
trust me is neither of that because it happens randomly.. could happen after 1500 requests or it could happen after 100 requests!
Re: issues after timeout
by wodDamir, Wednesday, May 19, 2010, 18:43 (5300 days ago) @ Klinzter
Klintzer,
And did you try our samples? Does it happen with it?
Are all GET requests done on same server? Are you sure that server doesn't deny requests if a lot of them arrives from the same user?
Regards,
Damba
Re: issues after timeout
by Klinzter, Wednesday, May 19, 2010, 18:46 (5300 days ago) @ wodDamir
Klintzer,
And did you try our samples? Does it happen with it?
Are all GET requests done on same server? Are you sure that server doesn't deny requests if a lot of them arrives from the same user?
Regards,
Damba
yes I am using your samples.. all requests on the same server and it doesnt deny requests from the same user...
one thing that I noticed is that (Response.Body) has the same data over and over..
Re: issues after timeout
by Klinzter, Wednesday, May 19, 2010, 19:15 (5300 days ago) @ Klinzter
so yes like I was saying I can see from the server logs that the app is sending the request to the server correctly but its showing the old data with (Response.Body) so is there a way to reset it back?
Re: issues after timeout
by wodDamir, Wednesday, May 19, 2010, 19:32 (5300 days ago) @ Klinzter
Klintzer,
Response.Body isn't reset when Socket error occurs. You can check Disconnected event if such an error occured, and set it to an empty string if you need.
What happens if you do GET on some other address when that error starts happening?
Regards,
Damba
Re: issues after timeout
by Klinzter, Wednesday, May 19, 2010, 21:07 (5300 days ago) @ wodDamir
Klintzer,
Response.Body isn't reset when Socket error occurs. You can check Disconnected event if such an error occured, and set it to an empty string if you need.
What happens if you do GET on some other address when that error starts happening?
Regards,
Damba
it does the same thing.. error 10053
Re: issues after timeout
by wodDamir, Wednesday, May 19, 2010, 23:29 (5300 days ago) @ Klinzter
Klintzer,
Is there any chance we can reproduce this issue on our side?
You mentioned that you are using our samples. Can we try doing a Get on the same page in order to reproduce this?
Regards,
Damba
