Configure whether the {@link StompBrokerRelayMessageHandler} should start automatically when the Spring ApplicationContext is refreshed. <p>The default setting is {@code true}.
Set the login to use when creating connections to the STOMP broker on behalf of connected clients. <p>By default this is set to "guest".
Set the passcode to use when creating connections to the STOMP broker on behalf of connected clients. <p>By default this is set to "guest".
Set the STOMP message broker host.
Set the STOMP message broker port.
Set the maximum interval, in milliseconds, at which the "system" relay session expects, in the absence of any other data, to receive a heartbeat from the STOMP broker. A value of zero will configure the relay session to expect not to receive heartbeats from the broker. <p>The default value is 10000.
Set the interval, in milliseconds, at which the "system" relay session will, in the absence of any other data being sent, send a heartbeat to the STOMP broker. A value of zero will prevent heartbeats from being sent to the broker. <p>The default value is 10000.
Set the login for the shared "system" connection used to send messages to the STOMP broker from within the application, i.e. messages not associated with a specific client session (e.g. REST/HTTP request handling method). <p>By default this is set to "guest".
Set the passcode for the shared "system" connection used to send messages to the STOMP broker from within the application, i.e. messages not associated with a specific client session (e.g. REST/HTTP request handling method). <p>By default this is set to "guest".
Set a destination to broadcast messages to user destinations that remain unresolved because the user appears not to be connected. In a multi-application server scenario this gives other application servers a chance to try. <p>By default this is not set. @param destination the destination to broadcast unresolved messages to, e.g. "/topic/unresolved-user-destination"
Set a destination to broadcast the content of the local user registry to and to listen for such broadcasts from other servers. In a multi-application server scenarios this allows each server's user registry to be aware of users connected to other servers. <p>By default this is not set. @param destination the destination for broadcasting user registry details, e.g. "/topic/simp-user-registry".
Set the value of the "host" header to use in STOMP CONNECT frames. When this property is configured, a "host" header will be added to every STOMP frame sent to the STOMP broker. This may be useful for example in a cloud environment where the actual host to which the TCP connection is established is different from the host providing the cloud-based STOMP service. <p>By default this property is not set.
Registration class for configuring a {@link StompBrokerRelayMessageHandler}.
@author Rossen Stoyanchev @since 4.0