Status/Resolution/Reason: Closed/Withdrawn/Duplicate
Reporter/Name(from Bugbase): Aaron Shurmer / Aaron Shurmer (Aaron Shurmer)
Created: 11/20/2012
Components: Web Container (Tomcat)
Versions: 10.0
Failure Type: Non Functioning
Found In Build/Fixed In Build: Final /
Priority/Frequency: Major / Some users will encounter
Locale/System: English / Win 2008 Server x64
Vote Count: 4
Duplicate ID: CF-3488063
Problem Description:
Having recently upgraded to cf10 standard, I've also hit a bit of a wall with what seems to be an iis 7 connector issue.
I'm running the updater 5, with correctly configured connector for that update, and IIS redirected 404 pages intermittently fail - about a 90% failure rate. failures only occur for remote browsers - probably due to IIS setting for custom error pages or detailed error pages for local browsers.
An example page is http://www.currentlyoffline.co.nz/servercheck
The setup here is IIS sees a 404, and the error page is set in IIS to 'Execure a URL on this site" being a .cfm file in the root dir of the site.
The IIS - > CF redirect works perfectly, I can log CF handling the request, the issue is that 90% of the time the request never makes its way back to the browser - generally receiving 'Error 101 (net::ERR_CONNECTION_RESET): The connection was reset'
I'm going to guess that this is another as yet unfixed bug in the connector, has anyone else seen such a problem / have any idea how to fix it?
Additional info:
The debug mode on the connector showed nothing exciting - the only error in there seems unrelated time wise but is:
[error] HttpExtensionProc::jk_isapi_plugin.c (2314): failed to init service for request.
I've also tried turning off the buffering in the connector - had no effect.
Steps to Reproduce:
In IIS set error 404 to 'Execure a URL on this site" being a .cfm file in the root dir of the site.
make that file return some data
hit the 404 from a remote browser / machine
Actual Result:
about 90% of the time you will get an:
Error 101 (net::ERR_CONNECTION_RESET): The connection was reset
Expected Result:
Any Workarounds:
front end url redirection so that IIS is purely doing the redirect not the execute fixes the problem - points to the problem being the connectors handling of the execution redirect that IIS is giving it.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3368804
External Customer Info:
External Company:
External Customer Name: AaronShurmer
External Customer Email:
External Test Config: My Hardware and Environment details:
Attachments:
Comments: