Hi James,
I'm not aware of any JMS-level configuration to do it. From an MDB perspective, the spec
states that message ordering is not guaranteed by the container. Message ordering is typically an application-level concern. It's best handled by using a database to track the intra-message relationships/state. Your application is in the best position to understand the
semantics of the message dependencies, and that way the application can work independent of the order in which the messages are delivered.
Other than the redelivery issue you've seen, there are two other problems with approximating
serialized delivery by setting the number of endpoints to 1. The first is reduced performance.
One of the benefits of MDBs is the ability to concurrently process messages. Second, if your
application assumes a single thread of serialized delivery it can't be deployed to a cluster.
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=316333