Socket创建后立即关闭问题求助：GUI中Thread子类NetUtils通信实现

Hey Mike, let's break down why your Socket is closing right away and fix it step by step. The core issue here is likely how you're managing the lifecycle of your NetUtils thread and the Socket itself—since you're extending Thread, you need to make sure the Socket logic lives in the right place and the thread is actually started.

1. Make Sure NetUtils Properly Overrides run() #

When you extend Thread, the only method that gets executed when you start the thread is run(). If you didn't override this method, the thread will just run an empty default implementation and terminate immediately, taking your Socket with it. Even if you did override it, creating the Socket outside of run() will cause it to get cleaned up once the constructor finishes.

Here's a corrected NetUtils implementation:

public class NetUtils extends Thread {
    private final String ip;
    private final int port;
    private Socket socket;

    // Initialize connection details in constructor
    public NetUtils(String ip, int port) {
        this.ip = ip;
        this.port = port;
        // Don't create the Socket here—save that for run()
    }

    @Override
    public void run() {
        try {
            // Create the Socket INSIDE run() to tie it to the thread's lifecycle
            socket = new Socket(ip, port);
            System.out.println("Successfully connected to: " + socket);

            // Set up input/output streams for communication
            BufferedReader input = new BufferedReader(
                new InputStreamReader(socket.getInputStream())
            );
            PrintWriter output = new PrintWriter(
                socket.getOutputStream(), true // Auto-flush enabled
            );

            // Keep the thread alive to listen for incoming messages
            String incomingMessage;
            while ((incomingMessage = input.readLine()) != null) {
                System.out.println("Received from server: " + incomingMessage);
                
                // If you need to update the GUI with this message, use SwingUtilities.invokeLater
                // to switch back to the EDT (Event Dispatch Thread)
                SwingUtilities.invokeLater(() -> {
                    // Example: Update a text field in your Window
                    // yourWindowTextField.setText(incomingMessage);
                });
            }

        } catch (IOException e) {
            System.err.println("Connection error: " + e.getMessage());
            e.printStackTrace();
        } finally {
            // Clean up resources when the thread exits
            try {
                if (socket != null && !socket.isClosed()) {
                    socket.close();
                    System.out.println("Socket closed gracefully");
                }
            } catch (IOException e) {
                e.printStackTrace();
            }
        }
    }
}

2. Don't Forget to Start the NetUtils Thread #

In your Window constructor, you're creating a NetUtils instance—but if you don't call start() on it, the thread will never run, and any Socket you created (if you were creating it in the constructor) will be discarded once the constructor finishes executing.

Update your Window class:

public class Window extends JFrame {
    private NetUtils comms;

    public Window() {
        // Initialize your GUI components first...
        
        // Create the NetUtils instance
        comms = new NetUtils("192.168.1.1", 288);
        // START THE THREAD! This triggers the run() method
        comms.start();
    }
}

3. Critical: Keep Socket Logic Off the EDT #

Your GUI runs on the Swing Event Dispatch Thread (EDT)—never do blocking operations (like Socket reads/writes) on this thread, as it will freeze your UI. By putting all Socket logic in NetUtils's run() method, you're ensuring it runs on a separate background thread, which is exactly what you want.

4. Bonus: Handle Thread Shutdown Gracefully #

If you need to close the Socket manually (like when the user closes the GUI), add a method to NetUtils to trigger the shutdown:

public void shutdown() {
    try {
        if (socket != null && !socket.isClosed()) {
            socket.close();
        }
    } catch (IOException e) {
        e.printStackTrace();
    }
}

Then call this from your Window's close handler:

this.setDefaultCloseOperation(JFrame.DO_NOTHING_ON_CLOSE);
this.addWindowListener(new WindowAdapter() {
    @Override
    public void windowClosing(WindowEvent e) {
        comms.shutdown();
        dispose();
        System.exit(0);
    }
});

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