users@glassfish.java.net

JMS_SUN_DMQ_UNDELIVERED_EXCEPTION DMQ message property bug?

From: <glassfish_at_javadesktop.org>
Date: Wed, 12 Mar 2008 15:08:15 PST

I throw a RuntimeException("message") from the MDB and after EndpointExceptionRedeliveryAttempts it is placed in the DMQ like it should be.

However, the JMSXDeliveryCount
 is 0 and should be 3. My trace statements clearly indicate 3 failed deliveries so I think this value should be 3, not 0.

Also, the JMS_SUN_DMQ_UNDELIVERED_EXCEPTION property doesn't exist. I'd expected it to contain my RuntimeException() or some useful data.

Is additional configuration required to enable these properties or is this a bug?

My message header in the DMQ:

JMSXDeliveryCount: 0
JMS_SUN_DMQ_BODY_TRUNCATED: false
JMS_SUN_DMQ_UNDELIVERED_REASON: UNDELIVERABLE
JMS_SUN_DMQ_PRODUCING_BROKER: mq://10.10.18.41:7676/?instName=imqbroker&brokerSessionUID=6572749278498210048
JMS_SUN_DMQ_DEAD_BROKER: mq://10.10.18.41:7676/?instName=imqbroker&brokerSessionUID=6572749278498210048
JMS_SUN_DMQ_UNDELIVERED_COMMENT: [B0055]: Message on destination Q:HubToFabSgp01Queue was Undeliverable
JMS_SUN_DMQ_UNDELIVERED_TIMESTAMP: 1205360983646
[Message sent by forum member 'frenchdrip' (frenchdrip)]

http://forums.java.net/jive/thread.jspa?messageID=263692