"szhigunov" wrote : | My understanding, that if transacted session is used, JMS guarantees that any given message delivered only once. | |
Not quite. If you consume a message in a tx, *and that tx is committed* then the message is guaranteed to never be delivered again. But in your case the tx is never committed, it is rolled back. Rollback causes redelivery (see JMS spec). It's the recovery manager (I assume you're using JBoss TS), not JBM that decides to commit or rollback. In this case it decides to rollback. Most probably another transaction branch in the same XA transaction failed to prepare (the database update) so this would be correct behaviour. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183393#4183393 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183393 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
