https://bz.apache.org/bugzilla/show_bug.cgi?id=59253
--- Comment #4 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to jfclere from comment #2) > 32, 104 and 113 are errno on linux > #define EPIPE 32 /* Broken pipe */ > #define ECONNRESET 104 /* Connection reset by peer */ > #define EHOSTUNREACH 113 /* No route to host */ If you are fortunate enough to have perror (binary) available, it will tell you that as well, including what kind of error code it is. $ perror 32 104 113 OS error code 32: Broken pipe OS error code 104: Connection reset by peer OS error code 113: No route to host (In reply to Remy Maucherat from comment #3) > The exception catch strategy is different in websockets (the servlet > container is more complex and catches and routes all these exceptions). > Nothing seems abnormal to me at this point, so it could be an enhancement. "Broken pipe" and "Connection reset" seem like normal "client disappeared" situations where handling it like EOF is probably just fine. That last one -- "No route to host" -- is a little weird. Does that happen when there is a network problem while trying to send bytes down an established channel? I've never seen that error during a conversation... only during an initial connection (attempt). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
