NodeJS stops responding after 11 requests?

I think the problem is the async call "pg. Connect" in a for loop. Try this js module async.

Sorry for the late come back. I found what was the problem but don't completely understand it. In the connect loop, I was using functions which were actually only simulating values (normally captured by a request).

This was the problem. If you don't issue any database request in the pg. Connect and loop on it, it seems the connections do not close properly.So the connection pool apparently breaks.

Hope I've been clear enough. Anyway thank you for your help.

Note that the message of sys. Puts may be incorrect - the server is only guaranteed to be listening once the (optional) callback function for listen fires. See: nodejs.org/docs/latest/api/http.html#server.Listen – Gijs Dec 16 '11 at 11:56 Didn't know .

Listen was async, thanks for the tip. – Elendir Dec 16 '11 at 17:02.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.