Java客户端传值至服务器异常，点击发送按钮程序崩溃求助

Hey there, let's dig into why your Java client-server app is crashing when you hit that send button. Since you mentioned you have Client.java, Server.java, and error logs, let's start with the most common culprits first—these are the usual suspects in button-click crashes for networked apps:

1. UI Thread Blocking (The #1 Culprit for Swing/AWT Apps) #

If you're doing network operations (like creating a Socket, reading/writing streams) directly inside your button's ActionListener, you're blocking the Event Dispatch Thread (EDT). The EDT handles all UI updates, and blocking it doesn't just make your app unresponsive—it can lead to hard crashes or deadlocks.

How to check & fix:
Look at your button click handler code. If you see something like new Socket("localhost", 8080) or stream reads/writes directly in the actionPerformed method, move that logic to a separate background thread. Use SwingWorker (for Swing apps) or a plain Thread to keep the EDT free:

sendButton.addActionListener(e -> {
    // Never block the EDT with network calls!
    new Thread(() -> {
        try (Socket clientSocket = new Socket("localhost", 8080)) {
            // Your data sending/validation logic here
            OutputStream out = clientSocket.getOutputStream();
            out.write(yourInputValue.getBytes());
        } catch (IOException ex) {
            // Don't swallow exceptions—log them!
            ex.printStackTrace();
        }
    }).start();
});

2. Uncaught Exceptions in Event Handlers #

The EDT doesn't handle uncaught exceptions gracefully. If your button click code throws an exception that's not caught, it'll crash the entire app immediately.

How to check & fix:
Wrap all code in your ActionListener with a full try-catch block, or set a global uncaught exception handler to capture crashes before they take down the app:

// Add this somewhere early in your client app (like main())
Thread.setDefaultUncaughtExceptionHandler((thread, ex) -> {
    System.err.println("Crash detected in thread: " + thread.getName());
    ex.printStackTrace(); // This will show you exactly where the problem is
});

This will print a detailed stack trace instead of just crashing—critical for pinpointing the issue.

3. Network Connection Failures #

If your server isn't running, uses the wrong port, or your firewall blocks the connection, the client will throw a ConnectException when trying to send data. Without a try-catch, this will crash the app.

How to check:

• Double-check that your server is started before the client
• Verify the port number matches exactly in both Client.java and Server.java
• Ensure no other program is using the port (use netstat -ano on Windows or lsof -i :<port> on macOS/Linux to check)

4. Resource Leaks #

If you're creating new Socket instances or streams every time you click the button but never closing them, you'll eventually run out of system resources (like file descriptors) and crash.

How to check & fix:
Always use try-with-resources for network resources—it automatically closes them when done:

// try-with-resources ensures Socket is closed even if an exception occurs
try (Socket clientSocket = new Socket("localhost", 8080);
     OutputStream out = clientSocket.getOutputStream()) {
    out.write(yourData.getBytes());
} catch (IOException ex) {
    ex.printStackTrace();
}

One final note: share the full error log stack trace! It'll tell you exactly what exception is being thrown and which line of code is causing the crash. If you can also post the relevant snippets from Client.java (the button click handler) and Server.java (the data receiving logic), I can give you a much more targeted fix.

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