When Setting a CLIENT ID String, WebLogic Throws 'Unexpected Response From Leader' Error When Trying to Enforce via WebLogic Connection Factory
(Doc ID 1586539.1)
Last updated on JULY 25, 2022
Applies to:Oracle WebLogic Server - Version 10.3.5 and later
Information in this document applies to any platform.
When setup a CLIENT_ID in JMS Client ID throws 'Unexpected response from leader' Error when trying to enforce via WebLogic connection factory.
When starting a producer, there are multiple TCP connections made and the following errors are thrown when trying to connect (for example) to JMS Servers 1; 2, but JMS Server 3 allows the connection to succeed and registers the CLIENT_ID String successfully.
The issue can be reproduced at will with the following steps:
1. Configured a connection factory with the CLIENT_ID string set to a unique value. CLIENT_ID_POLICY is set to be restricted and RECONNECT_POLICY is set to NONE.
2. Cluster Unicast: Consensus Leasing must be configured.
NOTE: Consensus leasing causes a cluster master (also known as coordinator) to be chosen in the cluster.
3. Admin Channel must be configured.
4. Trying to enforce only 1 JMS Producer connection to a specific JMS Resource using this specific JMS Connection Factory.
For example, having a Java client perform the following command.
java QueueSendProp t3://<IP1>:<PORT1>,<IP2>:<PORT2>,<IP3>:<PORT3>
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document