On Sun, Jun 30, 2013 at 11:35 AM, Jonahss <jona...@gmail.com> wrote: >> I know this error was previously ignored before 0.10, but I'd like to know >> what's causing this and how I can fix it/debug it? >> Is it a problem on our end (server) closing connections too soon?
Wireshark the connection, its usually pretty obvious what about the TCP exchange pattern is causing a reset when you see the packets. One common cause is timing, the server might be doing a close() instead of a shutdown(WRITE) (.end() in node), and the clients data arrives after the close sometimes, and before at other times. If its after, the connection is reset by the stack. Small changes in ordering of operations (node's write of buffers, o/s scheduling when client and server are running on the same system, system load, etc. can cause what is essentially a bug in the use of TCP to appear or go away). -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
