http://bugzilla.qos.ch/show_bug.cgi?id=105 noreply.ceki@qos.ch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #2 from noreply.ceki@qos.ch 2008-03-04 19:41 ------- Joern, I had a similar problem with hanging sockets in a different but very similar context. I has a web-app named SINK which contained the equivalent of SocketServer and numerous clients using the equivalent of SocketAppender. Moreover, it was a *hard* requirement for the clients to send messages to the SINK. For example, if the SINK web-app was not available, the clients would simply stop working. Thus, it was important that the clients successfully *reconnect* to the SINK web-app as soon as it became available. In turns out that the solution was to properly close all the sockets opened on the SINK (including the serverSocket). There was no need to close the socket on the client side after an exception as you are suggesting in your patch. Does the above apply or make sense in your case? Obviously, your patch is still applicable notwithstanding the above discussion. I am looking into it. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.