Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does IISnode timeout the Http Request #555

Open
gwadhwa opened this issue Jan 4, 2017 · 11 comments
Open

Does IISnode timeout the Http Request #555

gwadhwa opened this issue Jan 4, 2017 · 11 comments

Comments

@gwadhwa
Copy link

gwadhwa commented Jan 4, 2017

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.

@rramachand21-zz
Copy link
Collaborator

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

@gwadhwa
Copy link
Author

gwadhwa commented Jan 4, 2017

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
Copy link
Author

gwadhwa commented Jan 4, 2017

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

@gwadhwa
Copy link
Author

gwadhwa commented Jan 4, 2017

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

Please help!.

@rramachand21-zz
Copy link
Collaborator

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

@gwadhwa
Copy link
Author

gwadhwa commented Jan 4, 2017

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

means 150 seconds... Still same error..

@gwadhwa
Copy link
Author

gwadhwa commented Jan 5, 2017

Any help is much appreciated...

@gwadhwa
Copy link
Author

gwadhwa commented Jan 6, 2017

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!.

@prateekbansalnitk
Copy link

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

@gwadhwa
Copy link
Author

gwadhwa commented Jan 28, 2017

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

thats fixed the issue.

@rohithgopi
Copy link

rohithgopi commented May 30, 2019

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"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants