Support user destinations with multiple app servers
This change adds support for broadcasting messages with unresolved user destinations so that other servers can try to resolve it. That enables sending messages to users who may be connected to a different server. Issue: SPR-11620
This commit is contained in:
@@ -1741,6 +1741,13 @@ http://activemq.apache.org/delete-inactive-destinations.html[configuration optio
|
||||
for purging inactive destinations.
|
||||
====
|
||||
|
||||
In a multi-application server scenario a user destination may remain unresolved because
|
||||
the user is connected to a different server. In such cases you can configure a
|
||||
destination to broadcast unresolved messages to so that other servers have a chance to try.
|
||||
This can be done through the `userDestinationBroadcast` property of the
|
||||
`MessageBrokerRegistry` in Java config and the `user-destination-broadcast` attribute
|
||||
of the `message-broker` element in XML.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user