Hi,\r\n\r\nI am currently working on a Server/Client application on a cluster\r\n\r\nI am running about 100 clients in parallel and one server (32 clients per node with 8 processor => 4 clients per processor) . The server is linked to all the clients via Sockets.\r\n\r\nAfter about 55 iteration (about 20 mins), i have a client dying and i receive the following error:\r\n\r\nClient 126 java.net.SocketException: Connection reset\r\n at java.net.SocketInputStream.read(SocketInputStream.java:168)\r\n at java.net.SocketInputStream.read(SocketInputStream.java:182)\r\n at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249)\r\n at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542)\r\n at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552)\r\n at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297)\r\n at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)\r\n at ServerClient.Server$TcpThread.run(Server.java:789)\r\nConnection reset\r\n\r\n\r\nthe Server.java.789 is : ServerThread.sockIn.readObject();\r\n\r\n\r\nDo you have any idea what could create the connection reset ? The other clients are still running. It seems that the client socket is creating an exception when we try to read a file which actually does not exist. \r\n\r\nMy main question is what are the method to identify the problem related to this specific socket (note that I am working on a cluster, hence accessing the node via ssh connection and without having admin access).\r\n\r\nI dont understand why suddenly one client would die. It was working well during 20 minutes and suddenly one die ? Do you have any idea and any advice on how to identify the reset of this Socket disconnection ?\r\n\r\nI though about using wireshark but the fact that the application is running on a cluster make it difficult to analyze,sniff the packets remotely. I dont know if i can do it remotely.\r\n\r\nDo you have any idea how I could debug this problem?\r\n\r\nThanks.