JMS_BEA_DeliveryFailureReason 2

Question

Hi,
We are seeing this error in some of our messages in our Error Queue.
Key = JMS_BEA_DeliveryFailureReason
Value = 2
We are running this on Oracle/ Weblogic 10.3.1
The architecture is we have an input Queue that receives messages.
A consumer reads these messages and passes them to an output queue.
On delivery failure Messages get moved to Error Queue.
What appears to be happening is that messages are getting moved directly from the Source queue to the Error Queue when the Source queue has "Consumption Paused". (we do this because the target system is down for maintenence). Messdages appear in the ErrorQueue when consumption of the queue shoudl mean that nothing is processing them,
When viewing these message via the console we see the following properties
JMS_BEA_DeliveryFailureReason     2     java.lang.Integer
JMSXDeliveryCount     0     java.lang.Integer
Has anybody seen this behaviour.
What do these error messages mean?
I can't find any references on the web to the meaning of these error messsages
Thanks,

Answer 1

"JMS_BEA_DeliveryFailureReason 2" means the message exceeded its delivery limit.
I agree that pause consumption should not affect the delivery count of messages. Sounds like a bug to me. I suggest that you report this to Oracle Support.