iisnode icon indicating copy to clipboard operation
iisnode copied to clipboard
verified publisher icon tjanczuk

Does IISnode timeout the Http Request

Open gwadhwa opened this issue 9 years ago • 11 comments

I see Http 500 error when server takes more than 30 sec to respond.

I checked all the properties in IIS but seems no issue.

Please help.

gwadhwa avatar Jan 04 '17 20:01 gwadhwa

You need to use these settings <attribute name="maxNamedPipeConnectionRetry" type="uint" defaultValue="100"/> <attribute name="namedPipeConnectionRetryDelay" type="uint" defaultValue="250"/>

rramachand21-zz avatar Jan 04 '17 20:01 rramachand21-zz

tried everything.

Here is my settings....still getting Error when response cross 30 seconds.

iisnode node_env="development" asyncCompletionThreadCount="0" nodeProcessCountPerApplication="1" nodeProcessCommandLine="%programfiles%\nodejs\node.exe" interceptor=""%programfiles%\iisnode\interceptor.js"" maxConcurrentRequestsPerProcess="1024" maxNamedPipeConnectionRetry="100" namedPipeConnectionRetryDelay="150" maxNamedPipeConnectionPoolSize="512" maxNamedPipePooledConnectionAge="300000" initialRequestBufferSize="100096" maxRequestBufferSize="6553600" uncFileChangesPollingInterval="5000" gracefulShutdownTimeout="60000" debuggingEnabled="false" debuggerPathSegment="debug" debuggerPortRange="5058-6058" maxLogFileSizeInKB="128" loggingEnabled="false" devErrorsEnabled="false" flushResponse="false" watchedFiles="*.js" promoteServerVars="APP_POOL_ID,UNMAPPED_REMOTE_USER,LOGON_USER,HTTP_VERSION,REMOTE_PORT,REMOTE_ADDR,REMOTE_HOST,LOCAL_ADDR,AUTH_USER,AUTH_TYPE,SERVER_PORT,APPL_PHYSICAL_PATH,CONTENT_TYPE,HTTP_HOST,HTTP_METHOD,HTTP_USER_AGENT"

gwadhwa avatar Jan 04 '17 21:01 gwadhwa

please edit my above comment and you will see the settings i use.

gwadhwa avatar Jan 04 '17 21:01 gwadhwa

windows status from IIS log is 500.0 109 which means pipe has been ended.

Please help!.

gwadhwa avatar Jan 04 '17 21:01 gwadhwa

you have set maxNamedPipeConnectionRetry="100" namedPipeConnectionRetryDelay="150" .. this means your timeout would be 15000 millseconds or 15 seconds.

rramachand21-zz avatar Jan 04 '17 21:01 rramachand21-zz

Moved to maxNamedPipeConnectionRetry="1000" namedPipeConnectionRetryDelay="150"

means 150 seconds... Still same error..

gwadhwa avatar Jan 04 '17 21:01 gwadhwa

Any help is much appreciated...

gwadhwa avatar Jan 05 '17 18:01 gwadhwa

more detail scenario: posting a 100 MB data from client to server. it seems IIS node does not pass this request to node.exe. What I see is HTTP 500 error from IIS. sub status code is 109 which means pipe has been ended.

Why iisnode does not pass this request to node.exe, increased timeout as I mentioned above but nothing worked.

Please help!.

gwadhwa avatar Jan 06 '17 15:01 gwadhwa

Hi, Were you able to figure out a solution for this? I am stuck in a similar situation!

prateekbansalnitk avatar Jan 27 '17 17:01 prateekbansalnitk

Use the above to increase timout. We added nodeProcessCommandLine="%programfiles%\nodejs\node.exe --max_old_space_size=8000"

thats fixed the issue.

gwadhwa avatar Jan 28 '17 12:01 gwadhwa

I am also facing similar issue. Trying to download data close to 350 MB. Below is my webconfig. Please suggest.

  nodeProcessCountPerApplication="1"
  maxConcurrentRequestsPerProcess="1024"
  maxNamedPipeConnectionRetry="10000"
  namedPipeConnectionRetryDelay="250"      
  maxNamedPipeConnectionPoolSize="512"
  maxNamedPipePooledConnectionAge="30000"
  initialRequestBufferSize="100096" 
  maxRequestBufferSize="6553600"      
  nodeProcessCommandLine="%programfiles%\nodejs\node.exe --max_old_space_size=8000"

rohithgopi avatar May 30 '19 15:05 rohithgopi