Please respond...
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Acknowledgements-and-transacted-sessions-tp4652740p4675021.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I have a test case where I am using CLIENT_ACK on consumer side and also
using session.recovery()
In this case, message redelivery is expected, right ? (according to
http://activemq.apache.org/message-redelivery-and-dlq-handling.html)
and what if my consumer throws exception and continuous to ru
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
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 transa
> I am unsure about this, hence the question. If, all a transacted
> session would achieve, is to prevent the need for destroying the
> consumer then that would clear things up for me.
>
Yes, auto redelivery and dlq handling are the key differences between
the batch ack in a session.commit and an
On Mon, 28 May 2012 15:42:21 +0100, Gary Tully
wrote:
>there are two aspects to this:
>1) standard jms redelivery semantics. In activemq this is handled by
>the consumer, so client side.
>redelivery occurs on "transacted" sessions if there is a rollback or
>an exception processing the message.
>
there are two aspects to this:
1) standard jms redelivery semantics. In activemq this is handled by
the consumer, so client side.
redelivery occurs on "transacted" sessions if there is a rollback or
an exception processing the message.
While redelivery is in process, the message is not visible to
