On Apr 12, 10:53 am, Mark Hahn <[email protected]> wrote: > No one is going to be able to find your problem by you just describing > it. You are going to have to track down where you are losing it. > Norbert's suggestions sounded like a good start, especially putting in > timeout checks. > > Even if socket.io is losing it, which is quite unlikely, you will need to > find out where it is happening.
I'm not using socket.io, or whatever package to handle connections, I'm simply using http. And I sadly don't see how the timeout checks can help me. To me it sounds like if some packet were sent but the server was so busy handling other stuff (from other testservers) that simply dropped them and I was wondering if under the stress condition I'm putting the server this can happen. What I logged since the first time I experienced this problem is testserver waiting for answer at different stages of the test (remember function a/b/c/d? one of those) and eventually ending in timeout exception (socket timeout) and throwing an error. This error described where that happened, and there is not a unique point in which it's happening: it can happen in b as well as in c or d. That's why I'm confused, and I don't think Nob's suggestion (even though it was clever) is gonna help me somehow. Also, sorry Nob if I mispelled your name in my reply. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: 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 post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
