Timeout at 60 seconds?
10 posts
• Page 1 of 1
Timeout at 60 seconds?
Hi,
refering to this old thread:
http://www.helicontech.com/forum/15994- ... conds.html
Using the following proxy settings:
<Helicon>
ProxyConnectTimeout 120
ProxyReceiveTimeout 100
ProxySendTimeout 80
ProxySuppressErrors Off
</Helicon>
Using Version 3.1.0.78.
I was able to capture the error returned after 60 seconds.
HTTP/1.1 500 Internal Server Error
Date: Thu, 29 Nov 2012 07:42:02 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html
Content-Length: 206
Cache-Control: no-cache
Pragma: no-cache
<html><body>Error in ISAPI_Rewrite helper ISAPI extension.<br>12152 - The server returned an invalid or unrecognized response
<br>File: .\AsyncProxyContext.cpp, Line: 1093.<br/>Intrenal Error</body></html>
Will this help solve the issue my system is facing where timeout occurs at 60 seconds regardless of the higher proxysetting timeout values?
thanks.
refering to this old thread:
http://www.helicontech.com/forum/15994- ... conds.html
Using the following proxy settings:
<Helicon>
ProxyConnectTimeout 120
ProxyReceiveTimeout 100
ProxySendTimeout 80
ProxySuppressErrors Off
</Helicon>
Using Version 3.1.0.78.
I was able to capture the error returned after 60 seconds.
HTTP/1.1 500 Internal Server Error
Date: Thu, 29 Nov 2012 07:42:02 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html
Content-Length: 206
Cache-Control: no-cache
Pragma: no-cache
<html><body>Error in ISAPI_Rewrite helper ISAPI extension.<br>12152 - The server returned an invalid or unrecognized response
<br>File: .\AsyncProxyContext.cpp, Line: 1093.<br/>Intrenal Error</body></html>
Will this help solve the issue my system is facing where timeout occurs at 60 seconds regardless of the higher proxysetting timeout values?
thanks.
- tidaltides
-
- Posts: 24
- Joined: 27 Nov 2012, 21:57
Re: Timeout at 60 seconds?
It happens to me every once in a while. I'm not sure if there really is a permanent fix to it until now.
Re: Timeout at 60 seconds?
Firstly, could you please update to the latest build of ISAPI_Rewrite which is 95 at the moment.
If the problem persists after that, we'll continue investigating.
If the problem persists after that, we'll continue investigating.
Re: Timeout at 60 seconds?
Hello,
The error you get "The server returned an invalid or unrecognized response" implies that there might be a problem with server response, so it would be nice know what error is shown on the backend (there may be some details).
And, if the error occurs more or less frequently, you could use Fiddler to catch more info about this failing request.
The error you get "The server returned an invalid or unrecognized response" implies that there might be a problem with server response, so it would be nice know what error is shown on the backend (there may be some details).
And, if the error occurs more or less frequently, you could use Fiddler to catch more info about this failing request.
Re: Timeout at 60 seconds?
Kindly advise what you mean by "error shown on the backend"?
The error happens 100% of the time.
As long as it exceeds 60 seconds to return, that error will always appear.
The error happens 100% of the time.
As long as it exceeds 60 seconds to return, that error will always appear.
Re: Timeout at 60 seconds?
"error on the backend" means is there any error on the server that you are hiding behind proxy?
And please use Fiddler to get all the info you get upon such failing request and send the Fiddler log file to [email protected]
And please use Fiddler to get all the info you get upon such failing request and send the Fiddler log file to [email protected]
Re: Timeout at 60 seconds?
Hi,
There are no errors on the backend. The Server was still processing the request (its a search actually), and before it finished, the frontend already threw the error.
For example the search takes 80 seconds to return. The GUI gave up and returned the error at 60 seconds.
BTW the testing was done locally, i.e. no proxy.
Attached are the fiddler2 findings.
There are no errors on the backend. The Server was still processing the request (its a search actually), and before it finished, the frontend already threw the error.
For example the search takes 80 seconds to return. The GUI gave up and returned the error at 60 seconds.
BTW the testing was done locally, i.e. no proxy.
Attached are the fiddler2 findings.
- 01.JPG (167.5 KiB) Viewed 4334 times
- 02.JPG (219.91 KiB) Viewed 4334 times
Re: Timeout at 60 seconds?
Sorry, but it hardly possible to read Fiddler records in a screenshot.
Could you please send the entire Fiddler log file to [email protected]
Could you please send the entire Fiddler log file to [email protected]
10 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 41 guests