Message Driven Bean (MDB) Not Processing the Messages Concurrently from a JMS Queue
(Doc ID 2634884.1)
Last updated on FEBRUARY 20, 2024
Applies to:
Oracle WebLogic Server - Version 10.3.6 and laterInformation in this document applies to any platform.
Symptoms
A Message Driven Bean (MDB) with max-beans-in-free-pool element set as 2 is unable to process messages concurrently from JMS Queue.
Use Case
1. Create a JMS Queue
2. Deploy an MDB which consumes messages from the JMS Queue with max-beans-in-free-pool as 2
3. Put 2 messages on the Queue M1(large size message) followed by M2(small size message)
4. It was observed that M2 didn't process until M1 completes.
Changes
Deploy a Message Driven Bean (MDB) with max-beans-in-free-pool value as 2 that consumes messages from a 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 |
Changes |
Cause |
Solution |