Server Removed From Cluster View Due To PeerGone When JMS SAF Is Configured
Last updated on DECEMBER 11, 2017
Applies to:Oracle Weblogic Server - Version 9.2 to 10.3.2
Information in this document applies to any platform.
***Checked for relevance on 24-Oct-2012***
The servers are periodically dropping out of the cluster.
Log messages are shown below:
This issue only occurs with the specific configuration below:
DomainA configured with a SAFAgent that is configured to forward messages to a DistributedDestination on DomainB.
DomainB configured with a SAFAgent that is configured to forward messages to a DistributedDestination on DomainA.
Both DomainA and DomainB are configured with a cluster containing 2 managed servers.
DistributedDestination on DomainA is configured with the same JNDI name as DistributedDestination on DomainB. (This is the key requirement to cause this issue)
SAFRemoteContext is configured with t3s protocol in the destination URL. (Using t3 will not reproduce the issue)
The server names and resource names of DomainA are different from the server names and resource names on DomainB.
If you use t3 in the SAFRemoteContext destination URL instead of t3s, the problem will not occur.
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