DLQ ( dead letter) is for failed messages, so messages that are acked as poison - the consumer saying I cannot delivery this message, I have retried and it gets rolledback of there is an exception.
If there is client ack, then the message is acked. There is no DLQ processing. So DLQ processing is the result of a Poison Ack - another type of ack that indicates a (possibly repeated) failure by the app as seen by the message consumer On 29 November 2013 06:09, johnbing <bingjoh...@gmail.com> wrote: > As you have specified "Yes, auto redelivery and dlq handling are the key > differences between > the batch ack in a session.commit and an application initiated client > ack. (message.acknowledge) " > > I am able to under dlq handling prospective ? I got that redelivery can only > be achieved by using transactions. But what is the difference in DLQ > handling in transactions Vs Acknowledgement ? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Acknowledgements-and-transacted-sessions-tp4652740p4674935.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
