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 this really is not an option for us.
Other option is create a pool of consumers tied to it's sessions, and allowing only one message per consumer at a time, so i can rollback the single message. This adds the limitation of a fixed size number of workers (one worker per consumer). Unless a complex dynamic pooling mechanism is implemented. I'll try this second option of a pool. In my opinion, if the API of a message supports ACK, it is natural to have a NACK in the same level. Thanks for your time Tim! Jose Luis -- View this message in context: http://activemq.2283324.n4.nabble.com/Rollback-NACK-a-single-message-tp4674444p4674557.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
