My Oracle Support Banner

After MDB onMessage() Execution, JMS Messages Remain In JMS Queue (Doc ID 1546276.1)

Last updated on JULY 23, 2018

Applies to:

Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.

Symptoms

1. A  Java Message Service (JMS) queue and queue connection factory are configured in OC4J 10.1.3 as following : 

<queue-connection-factory location="MDBQCF" />

<queue name="jmsQueue"  location="jms/Queue"  persistence-file="MDB_File_QUEUE">


2. A Message Driven Bean (MDB) is dequeuing JMS messages from the defined Queue (jmsQueue).

The onMessage() method of this MDB bean has  the Required Transaction attribute.

The MDB  onMessage() method is well invoked and executed (JMS message is well received) .

3. The problem is that after onMessage() execution,  the JMS message,  which had been handled by the MDB bean,  still remains in the Queue .

 

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.