Spring MVC中如何处理Stomp JS客户端断开连接问题？

Handling both expected and unexpected STOMP client disconnections on your Java server side is absolutely doable, and it’s critical for maintaining clean user sessions and accurate online state tracking. Let’s break down how to cover both scenarios:

Handling Expected Disconnections (e.g., Browser Tab Closure) #

When a user intentionally closes a tab or logs out, you can make the STOMP client send a graceful DISCONNECT frame to the server.

First, add client-side logic to trigger this on page unload (building off your HTML/JS snippet):

window.addEventListener('beforeunload', () => {
  if (stompClient && stompClient.connected) {
    // Send graceful disconnect frame
    stompClient.disconnect(() => {
      console.log("Disconnected gracefully before tab closure");
    });
  }
});

On the Java server (assuming you’re using Spring Boot, the most common setup for STOMP/WebSocket):

• A clean approach is to override methods in StompSessionHandlerAdapter to catch graceful disconnects:

  public class CustomStompSessionHandler extends StompSessionHandlerAdapter {
    @Override
    public void afterDisconnected(StompHeaders headers, CloseStatus closeStatus) {
      String sessionId = headers.getSessionId();
      if (closeStatus.equals(CloseStatus.NORMAL)) {
        // Handle graceful expected disconnect (e.g., clean up user session, update online status)
        System.out.println("Session " + sessionId + " disconnected gracefully");
      }
    }
  }
  

Handling Unexpected Disconnections (e.g., Network Failure) #

For scenarios where the client can’t send a DISCONNECT frame (network drops, client crashes), you’ll rely on WebSocket heartbeat mechanisms to detect stale sessions.

Step 1: Configure Heartbeats in Your Java Server #

If using Spring Boot, update your WebSocketMessageBrokerConfigurer to enable heartbeats:

@Configuration
@EnableWebSocketMessageBroker
public class WebSocketConfig implements WebSocketMessageBrokerConfigurer {
  @Override
  public void configureMessageBroker(MessageBrokerRegistry config) {
    config.enableSimpleBroker("/topic")
          // Server sends heartbeat every 10s, expects client response within 10s
          .setHeartbeatValue(new long[]{10000, 10000});
    config.setApplicationDestinationPrefixes("/app");
  }

  @Override
  public void configureWebSocketTransport(WebSocketTransportRegistration registration) {
    registration.setTimeToFirstMessage(30000); // Drop session if no first message in 30s
  }
}

Step 2: Listen for Session Disconnect Events #

Spring fires a SessionDisconnectEvent whenever a WebSocket session drops (including heartbeat timeouts). Create a listener to handle this:

@Component
public class StompSessionDisconnectListener implements ApplicationListener<SessionDisconnectEvent> {
  @Override
  public void onApplicationEvent(SessionDisconnectEvent event) {
    String sessionId = event.getSessionId();
    CloseStatus closeStatus = event.getCloseStatus();

    if (closeStatus.equals(CloseStatus.TIMEOUT) || closeStatus.equals(CloseStatus.SERVER_ERROR)) {
      // Handle unexpected disconnect (e.g., mark user as offline, clean up resources)
      System.out.println("Session " + sessionId + " disconnected unexpectedly: " + closeStatus.getReason());
    }
  }
}

Key Notes #

• Framework Agnostic: If you’re using a non-Spring Java WebSocket framework (like Tyrus), the core logic is the same: enable heartbeats and listen for session termination events.
• Edge Cases: Some network proxies might drop idle connections faster than your heartbeat interval—test with your deployment environment to adjust timings.
• Session Tracking: Make sure you map STOMP session IDs to user IDs (e.g., via authentication headers) so you can associate disconnect events with specific users.

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