For one use case, when a exception causes a rollback, that exception is trapped. Have a peek at https://issues.apache.org/jira/browse/AMQ-3236 and the associated commits. We may be able to build on that.
On 19 January 2012 05:58, Jason Dillon <ja...@planet57.com> wrote: > Is there any easy way to get information about why a message had been sent to > ActiveMQ.DLQ? > > I'm seeing a bunch of messages sent to a virtual topic (as indicated by > OriginalDestination property while browsing the ActiveMQ.DLQ via visualvm, > which end up in the DLQ. Really unsure why any message sent to a virtual > topic would end up here. Shouldn't the virtual topic simply copy the message > to all known client's and be done with it? > > More generally though, is there any way to include detail in the message when > sent to the DLQ as to why it was sent there? > > --jason -- http://fusesource.com http://blog.garytully.com
