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.
On 11/15/2013 09:37 AM, jlpedrosa wrote:
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
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
On 11/15/2013 07:36 AM, jlpedrosa wrote:
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
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
Correct, NMS.ActiveMQ behaves the same as a JMS client so this should work.
On 11/14/2013 11:04 AM, Christian Posta wrote:
I'm not too familiar with the NMS libs... but for the Java JMS impl,
you would just throw an exception + combine with the redelivery policy
(eg, disable redelivery?) and tha
I'm not too familiar with the NMS libs... but for the Java JMS impl,
you would just throw an exception + combine with the redelivery policy
(eg, disable redelivery?) and that would send back the "poison pill"
or "nack"
On Thu, Nov 14, 2013 at 6:42 AM, jlpedrosa wrote:
> Hi All,We are coding an ap
