Durable Subscriber Reconnection Failure With The Default Client ID Policy Set to "Restricted" and The Subscription Sharing Policy Set to "Exclusive".
(Doc ID 1439386.1)
Last updated on JULY 15, 2021
Applies to:Oracle WebLogic Server - Version 10.3.4 and later
Information in this document applies to any platform.
**** Checked for relevance Dec 27th, 2013 ****
The following note delivers a patch to provide retro-compatibility when using Uniform Distributed Topics, using manual failover for Durable Subscriber, to emulate behavior existing in WebLogic Server versions prior 10.3.4. To understand what is the use case and if eventually this patch applies to your environment, please carefully read the use case described bellow.
The following is the JMS use case:
- Distributed topic across two managed servers.
- Producer sends a message to the cluster.
- Consumer connects durably to server A.
- Server A goes down.
- Consumer reconnects durably to server B.
- Server A is brought back online.
- Consumer now has two durable connections as the same subscriber as unable to consume messages.
All of this is using the default Client ID Policy to "Restricted" and Subscription Sharing Policy to "Exclusive".
Complete test case available in here.
Bellow a complete sequence of events:
1. ON MESSAGE CONSUMER SIDE
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