Non-Persistent Messages Being Enqueued As Persistent When Using AQ JMS
(Doc ID 413073.1)
Last updated on SEPTEMBER 08, 2022
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.2 and later
Oracle Containers for J2EE - Version 10.1.2.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
On DB 10.2.0.2.0 in Production:
Messages enqueued from java code with deliverymode=NON-Persistent are showing as Persistent.
This does work from pl/sql code, but not from java code.
Enqueuing the message as DeliveryMode.NON_PERSISTENT from the java code should be the same as from pl/sql.
The message should appear as IN-MEMORY in the queue, but it appears as READY.
Steps to reproduce the problem:
1. Create the AQ objects:
Here we will have the three messages with the MSG_STATE as READY.
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