most if not all of that info is available already. dlqDeliveryFailureCause property org.apache.activemq.command.Message#getOriginalDestination (currently not visible via a property) org.apache.activemq.command.Message#getBrokerInTime (System.currentTimeMillis()) via property JMSActiveMQBrokerInTime
The PutApplName thingy is missing, but you could use a DLQ per subscription for durable topic subs, maybe we can add the clientId of the sub as an additional property in some future enhancement, and make getOriginalDestination accessibe through some JMSActiveMQOriginalDestination What sort of PutApplName is in your mind from JMS? see the code at: https://github.com/apache/activemq/blob/trunk/activemq-broker/src/main/java/org/apache/activemq/broker/region/RegionBroker.java#L709 and https://github.com/apache/activemq/blob/trunk/activemq-broker/src/main/java/org/apache/activemq/util/BrokerSupport.java#L51 On 31 December 2013 08:48, rhuiser <[email protected]> wrote: > Greetings, > > How would I configure ActiveMQ as such when a message is moved to the DLQ, > the following headers are added to provide additional information? > > Reason -- Reason message arrived on dead-letter queue (the exception itself) > DestQName -- Name of original destination queue > PutApplName -- Name of application that put message on dead-letter queue > PutDate -- Date when message was put on dead-letter queue > PutTime -- Time when message was put on dead-letter queue > > The information (when added to the message as headers when moved to the DLQ) > would greatly improve troubleshooting in production environments. > > Any ideas? > > Thanks -- Robin > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/DLQ-headers-in-ActiveMQ-tp4675905.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
