You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@nutch.apache.org by Matt Zytaruk <ma...@wavefire.com> on 2005/12/15 21:06:03 UTC

Socket Exceptions

Does anyone ever get socket exceptions in the distributed searching? I 
am getting exceptions show up quite often when I run queries(though not 
always)
On the search node I am getting:
060126 051009 14 Server handler on 10050 caught: 
java.net.SocketException: Broken pipe
java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at 
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
        at 
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
        at java.io.BufferedOutputStream.write(BufferedOutputStream.java:79)
        at java.io.DataOutputStream.writeInt(DataOutputStream.java:175)
        at org.apache.nutch.ipc.Server$Handler.run(Server.java:209)
060126 051009 34 Server connection on port 10050 from 64.141.15.128: exiting


On the server running the nutchbean I get:
051215 114620 11 Client connection to 64.141.15.123:10050 caught: 
java.lang.NullPointerException
java.lang.NullPointerException
        at org.apache.nutch.ipc.Client$Connection.run(Client.java:158)

which leads to the server saying it's getting no response from the 
search node.

Anyone have any problems like this or know what the problem could be? 
This is using the mapred branch, and happens most when running 10 or so 
queries/second. Thanks for any help.

-Matt Zytaruk