We all have encountered this kind of problem with socket implementation (derived from the good old known BSD).
The only solution is to close the socket to have the read aborted and so the thread awaiked ;( And I don't speak about writing on half-closed socket where you get no error for a while since TCP stack the messages to be send (argh damn't BSD socket implementation) ;) >ideally :) i think the problem might be that once you're >blocked reading on >a socket, other than shutting down the socket (i.e. Socket.shutdown()), >there's no way to interrupt. i'm not 100% sure on that, >though. i need to >think about it some more... > > >> Those extra seconds required for shutdown count when you have to do >> a stop/start of tomcat on a production system. >> > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
