Keeping Ordering after message NACK ----------------------------------- Key: JBAS-2444 URL: http://jira.jboss.com/jira/browse/JBAS-2444 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public(Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.3 SP1 Reporter: Adrian Brock There is a common FAQ about how to keep message ordering in the event of failure (i.e. a NACK or transaction rollback). JMS gives no such guarantees. However, we could give that guarantee at the expense of throughput. Basically what we need to do is not allow anybody to receive() a message until the single message (or group of messages in the same transaction) that has already been received is either nacked or acked. Once the nack (rollback) comes from the client that has the "checked out" message it will be reinserted back into the Queue at the top of the list and then we allow the next receive() to run. Meaning it always the nacked message and can't get any other message until the top message is acked.