이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 32. Client Reconnection and Session Reattachment


HornetQ clients can be configured to automatically reconnect or re-attach to the server if a failure is detected in the server-client connection.

32.1. 100% Transparent session re-attachment

If failure is transient (that is, due to a temporary network failure) and the target server was not restarted, sessions will still exist on the server as long as the connection-ttl has not expired (see Chapter 15, Detecting Dead Connections for details about connection-ttl).
In this case, HornetQ automatically re-attaches the client sessions to the server sessions when the connection reconnects. This is done 100% transparently and the client can continue as before.
As HornetQ clients send commands to their servers, they store each sent command in an in-memory buffer. When connection failure occurs and the client re-attaches to its server, the server passes the ID of the last command it successfully received back to the client as part of the re-attachment protocol. If the client had attempted to send any other commands, it can resend those commands from its buffer so that client and server can reconcile their differences.
The ConfirmationWindowSize parameter (typically set in the <JBOSS_HOME>/jboss-as/server/<PROFILE>/deploy/jms-ra.rar/META-INF/ra.xml file) defines the size of the buffer in bytes. When the server has received ConfirmationWindowSize bytes of commands and processed them it will send back a command confirmation to the client. The client can then remove confirmed commands from the buffer.
Setting ConfirmationWindowSize to -1 (default) disables buffering and prevents re-attachment from occurring, forcing reconnect instead.
If you are using JMS, and the JMS service on the server is being used to load your JMS connection factory instances into JNDI, then uncomment the ConfirmationWindowSize parameter in the <JBOSS_HOME>/jboss-as/server/<PROFILE>/deploy/jms-ra.rar/META-INF/ra.xml file. If you are using JMS, but not JNDI, set these values directly on the HornetQConnectionFactory instance with the appropriate setter method. If you are using Core, you can set these values directly on the ClientSessionFactory instance with the appropriate setter method.
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat