Java Socket传输对象遇Connection Reset by Peer报错求解决

Hey there, sorry to hear you're stuck with this frustrating error while working on your university Socket server-client project for object transfer. Let's break down the most likely causes and walk through fixes to get you back on track.

First, a quick context: "Connection Reset by Peer" means one end of your Socket connection (either server or client) closed the link unexpectedly, or the communication got interrupted mid-transmission. From your server output Server started--1 Server started new connection , all conections ..., it looks like the connection was successfully established—so the problem is almost certainly happening after that, during the object transfer phase.

Here are the key areas to investigate:

1. Fix Socket Shutdown Logic #

Make sure both client and server are closing connections in an orderly, coordinated way:

• If your server closes the Socket immediately after receiving data, but the client is still trying to send more objects, you’ll trigger this reset error.
• For Java-based projects (common for object serialization), have the client call shutdownOutput() on the Socket after sending the last object—this tells the server there’s no more data coming, so it can safely process and close the connection without surprises.
• Avoid abrupt closes (like killing the client process without properly closing the Socket) as this will make the OS send an immediate RST packet to the server.

2. Validate Object Serialization #

Since you’re transferring objects, serialization mismatches are a top culprit:

• Ensure the object class you’re sending implements the required serialization interface (e.g., Serializable in Java) on both the client and server sides.
• Double-check that the class structure is identical across both ends: same package name, class name, fields, and (critical) same serialVersionUID if you’ve defined it. Mismatches here can cause silent deserialization failures that kill the connection.
• Test with a super simple object first (e.g., a Person class with just name and age fields) to rule out serialization as the problem.

3. Match Stream Initialization Order #

When using ObjectInputStream and ObjectOutputStream, the order of creation must be identical on both client and server. For example:

• Server side:

  Socket clientSocket = serverSocket.accept();
  ObjectInputStream ois = new ObjectInputStream(clientSocket.getInputStream());
  ObjectOutputStream oos = new ObjectOutputStream(clientSocket.getOutputStream());
  

• Client side must follow the exact same order (first ObjectInputStream, then ObjectOutputStream—or vice versa, but both ends have to match). Mixing this up will cause blocking or unexpected connection resets.

4. Rule Out Network/Environment Issues #

• Test with both client and server running on the same machine (use localhost as the server IP) to eliminate firewall, router, or cross-network problems.
• Check if any antivirus or firewall software is blocking the port you’re using—temporarily disable them for testing if needed.
• Confirm the server is listening on the correct port, and the client is connecting to the right IP/port combination.

5. Debug with Logs and Simplification #

• Add detailed logs at every step: log when the client sends an object, when the server receives it, when streams are opened/closed. This will help you pinpoint exactly where the connection is resetting.
• Strip down your code to the bare minimum: create a server that only reads one object and sends a response, and a client that only sends that object. If this simplified version works, gradually add back your project code to find what’s causing the issue.

内容的提问来源于stack exchange，提问作者Redon Bejtullahu