You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chat has been implemented using React JS with Spring Boot as the back-end. Relay to STOMP broker AWS Managed ActiveMQ service is enabled. The use-case is straight forward; chat has to be connected 24x7. Broker is setup in a active/standby configuration. As soon as there is a fail-over of active broker(url-1) the standby broker(url-2) kicks-in. A supplier of two addresses for active and standby is configured, the system fail-over is happening as expected.
However, the existing connections to Active Broker (chats) are not ported automatically to standby broker, rather, it's just disconnected in UI and a fresh Web Socket connection had to be requested. The reconnection logic is not implemented for Client sessions, but rather, only System connection.
The text was updated successfully, but these errors were encountered:
Chat has been implemented using React JS with Spring Boot as the back-end. Relay to STOMP broker AWS Managed ActiveMQ service is enabled. The use-case is straight forward; chat has to be connected 24x7. Broker is setup in a active/standby configuration. As soon as there is a fail-over of active broker(url-1) the standby broker(url-2) kicks-in. A supplier of two addresses for active and standby is configured, the system fail-over is happening as expected.
However, the existing connections to Active Broker (chats) are not ported automatically to standby broker, rather, it's just disconnected in UI and a fresh Web Socket connection had to be requested. The reconnection logic is not implemented for Client sessions, but rather, only System connection.
The text was updated successfully, but these errors were encountered: