EDN Uisng AQ: Orphaned Subscribers
(Doc ID 2587730.1)
Last updated on SEPTEMBER 05, 2024
Applies to:
Oracle SOA Suite - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
EDN is leaving behind orphaned subscribers. This appears to occur when a composite gets undeployed.
For e.g. there should only be 11 subscribers as evidenced by the EM. However, querying the AQ subscribers list returns 12 subscribers.
Due to the orphaned subscriber, the AQ tables continue to grow as the messages meant for the subscriber queue up and will never get consumed.
STEPS
-------------------
The BPEL project has a producer (EventProducer) that fires off events and a subscriber that listens to the event. The subscriber has a wait of 1 minute to simulate a still-executing process. To reproduce
1) Deploy project to SOA Server
2) Check EDN_AQJMS_TOPIC for subscribers. The new subscriber should show up there.
3) Using EM Test console, execute the EventProducer bpel. This will cause instances of the subscriber to be spawned off and running.
4) Immediately undeploy the composite.
5) Check the EDN_AQJMS_TOPIC and the subscriber will be left behind.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |