How "Server Affinity" works on JMS Distributed Destinations
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.0 and later
Information in this document applies to any platform.
When using the SERVER AFFINITY setting, how is the distribution of the JMS messages done every time a message is queued to a JMS DISTRIBUTED QUEUE?
"Server Affinity" is a concept widely used in distributed systems. In broad terms, it is a mechanism where the processing of client requests if forced to stick to a specific machine, not allowing any further processing linked to that request to be instatiated in (or moved to) any other machine but the one who started the chain. This generally means also the information for the request only lives and resides on the specific server, and is not distributed to other machines (which means, among other things, better performance).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms