java中tcp socket资源需按“流→socket→serversocket”逆序关闭，推荐用try-with-resources自动管理；若用try-catch-finally，须在finally中判空并捕获ioexception，确保资源不泄漏。
Java中用try-catch-finally管理TCP Socket连接，核心是确保Socket、InputStream、OutputStream和ServerSocket等资源在异常或正常执行后都能被正确关闭，避免端口占用、内存泄漏或连接堆积。
明确资源关闭顺序和责任归属
Socket相关资源需按“先打开、后关闭”的逆序释放：通常先关流（OutputStream、InputStream），再关Socket本身；如果是服务端，还要最后关闭ServerSocket。注意：调用socket.close()会自动关闭其关联的输入输出流，但显式关闭流更清晰、更安全（尤其在流被包装过时，如BufferedOutputStream）。
建议做法：
- 所有可关闭资源（Socket、InputStream、OutputStream、ServerSocket）声明为
final或放在try-with-resources兼容的位置 - 在
finally块中逐个判空并关闭，防止因某一步抛出NullPointerException中断后续关闭 - 关闭时捕获
IOException但不抛出——它属于清理阶段异常，一般记录日志即可，不应影响主流程
传统try-catch-finally写法（兼容Java 6+）
适用于不能使用try-with-resources的老版本或需精细控制关闭逻辑的场景：
ServerSocket serverSocket = null;
Socket clientSocket = null;
InputStream in = null;
OutputStream out = null;
try {
serverSocket = new ServerSocket(8080);
clientSocket = serverSocket.accept();
in = clientSocket.getInputStream();
out = clientSocket.getOutputStream();
// 处理请求，例如读取一行并返回响应
byte[] buffer = new byte[1024];
int len = in.read(buffer);
if (len > 0) {
out.write("HTTP/1.1 200 OK\r\n\r\nHello".getBytes());
out.flush();
}
} catch (IOException e) {
System.err.println("I/O error: " + e.getMessage());
} finally {
// 按逆序关闭：流 → Socket → ServerSocket
if (in != null) try { in.close(); } catch (IOException ignored) {}
if (out != null) try { out.close(); } catch (IOException ignored) {}
if (clientSocket != null) try { clientSocket.close(); } catch (IOException ignored) {}
if (serverSocket != null) try { serverSocket.close(); } catch (IOException ignored) {}
}
推荐：用try-with-resources（Java 7+）更简洁安全
自动管理资源生命周期，语义清晰、代码紧凑，且编译器保证即使构造函数抛异常，也不会触发未初始化资源的关闭操作：
try (ServerSocket serverSocket = new ServerSocket(8080);
Socket clientSocket = serverSocket.accept();
InputStream in = clientSocket.getInputStream();
OutputStream out = clientSocket.getOutputStream()) {
byte[] buffer = new byte[1024];
int len = in.read(buffer);
if (len > 0) {
out.write("HTTP/1.1 200 OK\r\n\r\nHello".getBytes());
out.flush();
}
} catch (IOException e) {
System.err.println("Connection error: " + e.getMessage());
}
注意：ServerSocket和Socket都实现了AutoCloseable，可直接用于try-with-resources；多个资源用分号分隔，关闭顺序与声明顺序相反。
客户端Socket的典型管理方式
客户端同样适用上述原则，区别在于通常不涉及ServerSocket：
Socket socket = null;
InputStream in = null;
OutputStream out = null;
try {
socket = new Socket("localhost", 8080);
in = socket.getInputStream();
out = socket.getOutputStream();
out.write("GET / HTTP/1.1\r\nHost: localhost\r\n\r\n".getBytes());
out.flush();
// 读响应...
byte[] resp = new byte[2048];
int n = in.read(resp);
System.out.write(resp, 0, n);
} catch (IOException e) {
System.err.println("Client I/O failed: " + e.getMessage());
} finally {
if (in != null) try { in.close(); } catch (IOException ignored) {}
if (out != null) try { out.close(); } catch (IOException ignored) {}
if (socket != null) try { socket.close(); } catch (IOException ignored) {}
}
或者更推荐：
try (Socket socket = new Socket("localhost", 8080);
OutputStream out = socket.getOutputStream();
InputStream in = socket.getInputStream()) {
out.write("GET / HTTP/1.1\r\nHost: localhost\r\n\r\n".getBytes());
out.flush();
// 读响应...
} catch (IOException e) {
e.printStackTrace();
}
关键不是语法多复杂，而是每次创建Socket及相关流时，都默认它需要被关闭——漏掉一次，就可能让连接卡在TIME_WAIT、端口无法重用，或服务器线程越积越多。
Java免费学习笔记：立即使用
解锁 Java 大师之旅：从入门到精通的终极指南
