Why does OracleAQ Leave Dead Subscribers in the Queue?
edited Apr 10, 2012 10:59PM in GoldenGate, Streams and Distributed Database (MOSC) 1 commentAnswered
I am on Oracle 11.2.0.3.
We've got a problem where we use Oracle's JMS over OracleAQ. This works fine except we started noticing the queue getting filled with 1000s, then millions of messages over time. Some of these are in the PROCESSED state, but most are READY. We traced down this behavior to "zombie" or dead subscribers to the topic. When a Java process is terminated and doesn't get the chance to unregister itself, it leaves the subscriber record in the queue and Oracle doesn't seem to detect that it is dead. So much so that MONTHS later, a new message sent into our multi-subscriber
0