the soLinger parameter was wrong.

With soLinger=true the httpd looses connections
The effect can be seen when crawling the internal repository:
lost connections filled the client process queue until it was full
and no more connections were possible.

git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@5620 6c8d7289-2bf4-0310-a012-ef5d649a1542

source/de/anomic/server/serverCore.java

@@ -379,8 +379,7 @@ public boolean job() throws Exception {
                 // controlSocket.setTcpNoDelay(true);
 
                 // set a non-zero linger, that means that a socket.close() blocks until all data is written
-                // controlSocket.setSoLinger(false, this.timeout);
-                controlSocket.setSoLinger(true, this.timeout);
+                controlSocket.setSoLinger(false, this.timeout);
 
                 // ensure that MTU-48 is not exceeded to prevent that routers cannot handle large data packets
                 // read http://www.cisco.com/warp/public/105/38.shtml for explanation