On Nov 21, 2005, at 6:45 PM, Gregory Woodhouse wrote:
More often than not, a connection reset indicates that there was a
"hard error" in the listening process (process that accepted the
connection). I'd go to the programmer (direct) mode prompt and type
D ^XTER
to view the error log.
BTW, a connection reset is the TCP equivalent of raising the white
flag. TCP does try to recover from most errors, but when a process
is unceremoniously killed before the connection can be shut down,
there's little that can be done. Technically, a reset means "throw
away all your state information and start over", but in this case,
"starting over" wouldn't lead anywhere. It is not at all uncommon for
processes to resynchronize, but a reset usually implies termination.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"Nothing is as powerful than an idea
whose time has come."
-- Victor Hugo
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
