Hi Tim
I will do that. Thanks!
Rgds
JL
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Rollback-NACK-a-single-message-tp467p4674559.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi
When I inspected the API, I thought about it, but it looks like for every
message I would need to create a session, and a consumer per message, which
sounds extremely heavy and we expect a significant amount of messages. (for
a given consumer I need a session to rollback that message), so thi
Hi All,This also leads to the same problem: the execution of the event must
be done in the same thread that ActiveMQ uses, otherwise I can't throw the
exception to the listener.
When the message arrives, I just put the message on a thread pool. That is
the approach to implement multi thread process
Hi!
First of all, Thanks for the support.
I am not really sure how to implement what you said:
I am actively listening to messages:
/consumer.Receive();/
So AFAIK I can't throw an exception up to NMS stack:
Are you suggesting that I listen in event mode? IE:
/consumer.Listener+=new MessageListene
Hi All,We are coding an application to process events in a queue. We are
using NMS - ActiveMQ 1.6.
In my mental model the best transactionality comes with:
IndividualAcknowledge.
If the proccess goes OK, the message is acknoledge, up to there no problem.
But message has no rollback/nack method. So
