QTcpServer重连问题：基于QTcpSocket的客户端服务端应用异常

Let's break down the root cause of your reconnection failure and fix it step by step:

Key Problems in Your Current Code #

• Critical server-side mistake: When a client disconnects, you're calling server->close() which stops the server from listening entirely. This means after the first client disconnects, your server can't accept any new connections—including reconnections from the same client. That's the main reason your reconnection isn't working.
• Redundant client-side call: In the client's disconnected() slot, tcpSocket->disconnectFromHost() is unnecessary. This signal is already emitted when the socket has lost connection to the host, so this call serves no practical purpose here.

Modified Working Code #

Server-side disconnected() Slot #

void testServer::disconnected() {
    QTcpSocket* socket = qobject_cast<QTcpSocket*>(sender());
    if (!socket) return; // Guard against invalid sender pointers
    
    qDebug() << " - CLIENT DISCONNECTED";
    socket->deleteLater(); // Properly clean up the disconnected client socket
    
    // Keep the server listening! Only restart if it stopped unexpectedly (optional)
    if (!server->isListening()) {
        if (!server->listen(QHostAddress::Any, yourServerPort)) {
            qDebug() << "Failed to restart server listening:" << server->errorString();
        } else {
            qDebug() << "Server resumed listening for new connections";
        }
    }
}

Client-side disconnected() Slot #

void testClient::disconnected() {
    qDebug() << " - SERVER DISCONNECTED";
    
    // Optional: Add automatic reconnection logic here
    // Example with a 2-second delay before retrying:
    // QTimer::singleShot(2000, this, [this](){
    //     tcpSocket->connectToHost(yourServerAddress, yourServerPort);
    // });
}

Explanation #

1. Server socket cleanup: When a client disconnects, you only need to clean up the specific socket tied to that client using deleteLater()—this ensures proper memory management without disrupting the server's ability to accept new connections.
2. Preserve server listening: Never close the QTcpServer instance unless you intentionally want to shut down the entire service. Keeping it listening is essential for handling reconnections.
3. Optional automatic reconnection: On the client side, adding a timer-based reconnection attempt makes your app more resilient to temporary network drops. You can adjust the delay and retry logic based on your needs.
4. Null pointer guard: The check for a valid socket prevents potential crashes if the signal sender isn't a valid QTcpSocket instance.

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