If you use an MDB, if the message fails it should go to the DLQ, you can configure this to happen after one try. (This isn't transactionally safe, from what I've heard.)
Alternatively, you could check the 'redelivered' flag on the message in an MDB. So: 1. MDB receives message 2. Do database processing, fails, roll back 3. Message redelivered ... instead of retrying the DB transaction, add the message to a different queue, consume the current message. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3893727#3893727 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3893727 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
