WebSockets & Real-Time Systems with Spring · Aula

Gestão do ciclo de vida das ligações

Faça a gestão dos ciclos de vida das ligações WebSocket, incluindo a abertura, o fecho e as desligações inesperadas.

Gestão do ciclo de vida das ligações é uma aula grátis de WebSockets & Real-Time Systems with Spring no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de WebSockets & Real-Time Systems with Spring, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de WebSockets & Real-Time Systems with Spring inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

WebSocket Connection Lifecycle

Every WebSocket connection goes through a lifecycle: it opens, stays active for messaging, and eventually closes. Managing these stages is crucial for building robust real-time applications.

Proper lifecycle management helps ensure resources are used efficiently and that your application responds gracefully to various connection events.

The Initial Handshake

Before a WebSocket connection is established, an initial HTTP handshake occurs. The client sends an HTTP request with an Upgrade header, asking to switch protocols.

If the server agrees, it responds with a 101 Switching Protocols status, and the connection transitions from HTTP to WebSocket.

Client-Side Connection

On the client side, typically in a web browser, you initiate a WebSocket connection using JavaScript. The WebSocket constructor creates a new connection to the specified URL.

This example shows how to connect and log messages when the connection opens or encounters an error.

const socket = new WebSocket("ws://localhost:8080/lifecycle");

socket.onopen = () => {
  console.log("WebSocket Connected!");
};

socket.onerror = (error) => {
  console.error("WebSocket Error:", error);
};

Server-Side: Handling New Connections

In Spring, you can use the @OnOpen annotation to define a method that executes when a new WebSocket connection is established. This is your entry point for handling new clients.

The Session object provides details about the client connection.

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Bean;
import org.springframework.stereotype.Component;
import org.springframework.web.socket.server.standard.ServerEndpointExporter;
import javax.websocket.OnOpen;
import javax.websocket.Session;
import javax.websocket.server.ServerEndpoint;

@SpringBootApplication
public class WebSocketLifecycleApp {
    public static void main(String[] args) {
        SpringApplication.run(WebSocketLifecycleApp.class, args);
    }

    @Bean
    public ServerEndpointExporter serverEndpointExporter() {
        return new ServerEndpointExporter();
    }
}

@ServerEndpoint("/lifecycle")
@Component
class LifecycleHandler {
    @OnOpen
    public void onOpen(Session session) {
        System.out.println("Client connected: " + session.getId());
    }
}

Gracefully Closing Connections

A connection can be closed intentionally by either the client or the server. This is called a 'graceful' closure. It's important to close connections properly to release server resources and inform clients.

A close message usually includes a status code and a reason for closure, helping both ends understand why the connection ended.

Client-Side Disconnect

Clients can close a WebSocket connection using the close() method. You can optionally provide a status code and a reason message.

The onclose event listener is triggered when the connection is closed, allowing you to perform cleanup or UI updates.

socket.onclose = (event) => {
  if (event.wasClean) {
    console.log(`Closed cleanly, code=${event.code}, reason=${event.reason}`);
  } else {
    console.log('Connection died unexpectedly');
  }
};

// To close the connection explicitly:
socket.close(1000, "Client leaving");

Server-Side: Handling Disconnections

The @OnClose annotation in Spring allows you to define a method that executes when a WebSocket connection is closed. This is where you can clean up resources associated with that session.

The CloseReason parameter provides details about why the connection was terminated.

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Bean;
import org.springframework.stereotype.Component;
import org.springframework.web.socket.server.standard.ServerEndpointExporter;
import javax.websocket.OnOpen;
import javax.websocket.OnClose;
import javax.websocket.Session;
import javax.websocket.CloseReason;
import javax.websocket.server.ServerEndpoint;

@SpringBootApplication
public class WebSocketLifecycleApp {
    public static void main(String[] args) {
        SpringApplication.run(WebSocketLifecycleApp.class, args);
    }

    @Bean
    public ServerEndpointExporter serverEndpointExporter() {
        return new ServerEndpointExporter();
    }
}

@ServerEndpoint("/lifecycle")
@Component
class LifecycleHandler {
    @OnOpen
    public void onOpen(Session session) {
        System.out.println("Client connected: " + session.getId());
    }

    @OnClose
    public void onClose(Session session, CloseReason reason) {
        System.out.println("Client disconnected: " + session.getId() + " - Reason: " + reason.getReasonPhrase());
    }
}

Handling Unexpected Disconnections & Errors

Sometimes connections don't close gracefully. Network issues, client crashes, or server errors can lead to abrupt disconnections. These are 'unclean' closures.

It's vital to have mechanisms to detect and respond to these unexpected events to maintain application stability and user experience.

Server-Side: Error Handling

The @OnError annotation handles exceptions that occur during a WebSocket session. This could be due to issues like message processing errors or underlying network problems.

Implementing an @OnError handler ensures your server can log errors and potentially close the affected session gracefully, preventing resource leaks.

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Bean;
import org.springframework.stereotype.Component;
import org.springframework.web.socket.server.standard.ServerEndpointExporter;
import javax.websocket.OnOpen;
import javax.websocket.OnClose;
import javax.websocket.OnError;
import javax.websocket.Session;
import javax.websocket.CloseReason;
import javax.websocket.server.ServerEndpoint;

@SpringBootApplication
public class WebSocketLifecycleApp {
    public static void main(String[] args) {
        SpringApplication.run(WebSocketLifecycleApp.class, args);
    }

    @Bean
    public ServerEndpointExporter serverEndpointExporter() {
        return new ServerEndpointExporter();
    }
}

@ServerEndpoint("/lifecycle")
@Component
class LifecycleHandler {
    @OnOpen
    public void onOpen(Session session) {
        System.out.println("Client connected: " + session.getId());
    }

    @OnClose
    public void onClose(Session session, CloseReason reason) {
        System.out.println("Client disconnected: " + session.getId() + " - Reason: " + reason.getReasonPhrase());
    }

    @OnError
    public void onError(Session session, Throwable throwable) {
        System.err.println("Error on session " + session.getId() + ": " + throwable.getMessage());
    }
}

Detecting Liveness with Heartbeats

When a connection drops unexpectedly (e.g., network cable pulled), neither side might immediately know. Heartbeat mechanisms, often using WebSocket ping/pong frames, help detect unresponsive peers.

By sending periodic pings and expecting pongs, you can determine if a connection is still alive and close it if no response is received.

Lifecycle Management Check

Managing the various stages of a WebSocket connection is key to building reliable real-time applications. Let's test your understanding of Spring's lifecycle annotations.

Recap: Connection Management

In this lesson, you've learned about the crucial aspects of WebSocket connection lifecycle management. We covered:

The initial HTTP handshake.
How clients and servers open connections (@OnOpen).
Graceful client and server disconnections (@OnClose).
Handling unexpected errors during a session (@OnError).
The role of heartbeats in detecting unresponsive connections.

Mastering these concepts is fundamental for developing robust and resilient real-time applications with WebSockets and Spring.

Perguntas Frequentes

A aula “Gestão do ciclo de vida das ligações” é grátis?

Sim — o texto completo de “Gestão do ciclo de vida das ligações” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de WebSockets & Real-Time Systems with Spring, atualize para CoddyKit PRO. O curso de WebSockets & Real-Time Systems with Spring inclui 4 aulas no total.

O que vou aprender em “Gestão do ciclo de vida das ligações”?

Faça a gestão dos ciclos de vida das ligações WebSocket, incluindo a abertura, o fecho e as desligações inesperadas. Você pratica WebSockets & Real-Time Systems with Spring com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar WebSockets & Real-Time Systems with Spring?

Nenhuma experiência prévia é necessária. WebSockets & Real-Time Systems with Spring no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Gestão do ciclo de vida das ligações”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de WebSockets & Real-Time Systems with Spring?

Sim. Cada aula de WebSockets & Real-Time Systems with Spring inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

Tratamento adequado de erros do WebSocket
Gestão do ciclo de vida das ligações
Novas tentativas e alternativas
Sinais de atividade e mensagens de manutenção Ping/Pong

← Voltar para WebSockets & Real-Time Systems with Spring