Unexpected exception in the selector loop. java.lang.Error: java.net.SocketException: Socket operation on nonsocket: getsockname ...

[Wesly smith]

So far (about 15 minutes), it worked fine.
Thanks

BTW, Trustin, I think I saw some other memory leak problem somewhere. I will
post later.

connect 1233721323049
connect closed 1233721323268
connect 1233721338269
connect closed 1233721338269
connect 1233721353271
connect closed 1233721353287
...
connect 1233721863928
connect closed 1233721863928
connect 1233721878929
connect closed 1233721878945
connect 1233721893946
connect closed 1233721893961
connect 1233721908962
connect closed 1233721908962

FYI, the revision that contains the complete workaround is: 749

— Trustin Lee, http://gleamynode.net/



On Wed, Feb 4, 2009 at 1:02 PM, Trustin Lee <trustin at gleamynode.net> wrote:
> I guess this is Windows-specific issue.  I've just checked in the work
> around for this issue.  The Error is thrown when a connection is
> closed by a remote peer very early.  Could you svn-up and let me know
> my workaround works for you?  I'd like to see what the result looks
> like soon.
>
> — Trustin Lee, http://gleamynode.net/
>

-- 
View this message in context: http://n2.nabble.com/Unexpected-exception-in-the-selector-loop.-java.lang.Error%3A-java.net.SocketException%3A-Socket-operation-on-nonsocket%3A-getsockname-...-tp2266877p2267141.html
Sent from the Netty User Group mailing list archive at Nabble.com.