Misunderstandings: 1) Your fundamental misunderstanding appears to be that messages are globally ordered. JMS guarantees that messages sent from a single sender are ordered. It says nothing about competing senders (your mdbs?). Though most jms providers use a form of timestamp so it generally works, but is subject to race conditions.
2) An MDB does not do a send until the transaction commits. This is outside your lock and so is also subject to race conditions. XASession -> onMessage -> lock -> send XASession -> commit -> send really happens here 3) That a QueueBrowser can see messages that are currently in the process of being sent to a client but have not yet been acknowledged by a client. It does not see these messages. If none of this applies use "READ THIS FIRST" to show me what IS happening. WARNING: If you dump pages of pages of logging with no context about how it matches what you are trying to do, I won't read it. I was originally interested in this post because I though you might have a bug. But it sounds like you don't understand (or are trying to bypass) the spec defined behaviour. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866108#3866108 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866108 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
