AQ Non-Durable subscribers not being removed when JMS application terminates abnormally
(Doc ID 2270171.1)
Last updated on MARCH 25, 2019
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
When a JMS application terminates abnormally without closing the message consumer, connection and session, any non-durable subscribers created during the execution of the application will remain associated to the queue. Subsequent messages enqueued in the queue for new durable subscribers will also be enqueued for the stale subscribers. As this messages are not consumed they cause the queue to grow in size over time generating performance problems for the dequeue operations and admin tasks executed on the queue.
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