Title:
Bug 85523:When a generate a 500 error (for example with a cffile read of a really big file), the request after is always a 503
| View in TrackerStatus/Resolution/Reason: Closed/Won't Fix/
Reporter/Name(from Bugbase): Erwan LOAEC / Erwan LOAEC (erloz)
Created: 01/06/2011
Components: General Server
Versions: 9.0.1
Failure Type: Unspecified
Found In Build/Fixed In Build: 9,0,1,274733 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Win All
Vote Count: 1
Problem:
When a generate a 500 error (for example with a cffile read of a really big file), the request after is always a 503.
Method:
Step to reproduce:call a CFM with:<cffile action="read" variable="content" file="C:\bigfile.content"><cfoutput>#content#</cfoutput>This generate a 500 error (we can find the OOM error on JRUN log)The next request to a mapped ressource pattern (*.cfm, /servlet/*, etc...) is always a 503. (no difference if the ressource exists or not)I've notice that the link between the IISconnector and JRUN stay in CLOSE_WAIT on the IIS side. If I manually kill the socket, I don't have this behaviour.If a enable verbose log on the connector, I cannot reproduce the bug.I cannot reproduce the case on CF8.
Result:
jrun_ii6_wildcard log error:2011-01-06 12:10:18 jrISAPI[3432:1388] returning error page for JRun too busy or out of memory
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3043033
External Customer Info:
External Company:
External Customer Name: Erwan LOAEC
External Customer Email: 758B13254D21A7CC0A746C19
External Test Config: 01/06/2011Attachments:
Comments: