Is There a Way to Track Failed Subscriber in Partitioned Distributed Topic Set-Up with One-Copy-Per-Application Model from Multiple JMS Topic Subscribers
(Doc ID 2814736.1)
Last updated on OCTOBER 18, 2023
Applies to:Oracle WebLogic Server - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Is there debug option or any configuration on WebLogic Server that would help find out which Subscriber failed in Partitioned Distributed Topic (DT) set-up; that uses one-copy-per-application model ?
Details of set-up and use-case:
Multiple Consumers are deployed to WebLogic (say; ConsumerA ; ConsumerB; ConsumerC; ConsumerD each targeted to a managed server respectively - total 4servers)
Partitioned DT configured with one-copy-per-application model and with 4 MDBs.
Failure scenario occur when a Message to reach ConsumerD (that is Active) and run into RaiseError that would prevent commit; causing RollBack.
When message fails on ConsumerD and placed in ErrorQ. With message in ErrorQ Redeliver will lead to duplicate request to Consumer A;B;C.
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