http result 408 , underlying connection is closing by server

[siliconplains]

I have a server that is node.js and a client written in .NET.  If I run a lot of instances of my client to scale test my server, the client throws an exception about the underlying connection is being closed unexpectedly on the .net web request getresponse call.  As well, we receive back a 408 http result.  Is there any way to keep that connection open longer so that the client has time to send through it's json payload post?

[Adrian Lynch]

Could you post some code? There are some people out there that'll click their fingers and know what the problem is straight away. There are others out there that like little problems like this and would love to give it a crack, but without code...

Does it work until under load?

Adrian

On 3 November 2014 20:24, siliconplains <wallan...@gmail.com> wrote:

I have a server that is node.js and a client written in .NET.  If I run a lot of instances of my client to scale test my server, the client throws an exception about the underlying connection is being closed unexpectedly on the .net web request getresponse call.  As well, we receive back a 408 http result.  Is there any way to keep that connection open longer so that the client has time to send through it's json payload post?

--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/fb52725e-8871-446a-ad72-accb4bf535c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[siliconplains]

Alright, so I narrowed it down.  I am running node under the new cluster module.  What is happening is one of the node processes is dying and it that is what is closing down the connection to the client.  It happens right before the node process response.  

This leads me to another couple of questions.  I am running node under the Webstorm debugger and I can't get all of the cluster processes to debug.  In fact, when I run node in a clusterd configuration as debug my client can't even connect to the debug clustered node server.  

Is there a way to get debugging to work with a clustered node server in webstorm?

Ok, now for figuring out what is crashing... Is there a way in node to report out the crash cause and stack when a cluster child crashes?  

Also, when you are running node in webstorm, how do you get it to write console output to a file?