I want to evaluate if this is proper usage of JMS. Hints or suggestions are appreciated.
Here's what i want to do: A message consumption and some database updates should be combined in a global transaction. (I have a queue-destination listener that receives and executes commands. The commands perform updates on a database connection) Now the question is: how to deal with commands that throw an exception. I should roll back the database updates. But i should mark the message somehow that it couldn't be executed (e.g. by moving the message to an error-queue or something...) One solution i see is to use 2 separate local transactions (1 for db and 1 for message consumption) instead of 1 global transaction. But of course, that could lead to inconsistent state in case of a server crash. Another solution might be using nested transactions. But does JBoss and/or JTA support that ? Any recommendation is appreciated. regards, tom. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3893572#3893572 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3893572 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
