Database JMS NonDurable Subscriber Issues
(Doc ID 417548.1)
Last updated on MARCH 05, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 9.2 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
This problem can occur on 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.
In the case of abnormal termination of a JMS client application which uses NonDurable subscribers you will be faced by the following symptoms
1. Non-durable subscriber entries are left orphaned in a queue table if the OJMS client terminates
2. Messages are left in a READY state until the orphaned subscriber is removed manually.
3. There is no way to distinguish between the messages associated with active consumers and those which are orphaned.
In the case of running a heavily loaded JMS NonDurable subscriber application you may see
1. High contention on the library cache load lock.
2. Intermittent slow downs which have the initial appearance of hangs.
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