AQ Non-Durable subscribers not being removed when JMS application terminates abnormally
Last updated on MAY 25, 2017
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms