"erik777" wrote : How about a link to information on how to: | | 1> Handle unavoidable exceptions in MDBs (highly unavoidable in today's distributed world where MDBs are expected to rely on remote services, such as the database, JNDI and web services.) I'm more than willing to catch these exceptions, if by catching I can ensure requirement #2: |
Force a rollback on error, which will happen anyway for RuntimeExceptions if the ejb transaction is linked to the delivery transaction (REQUIRED). anonymous wrote : | 2> Ensure 100% message reliability. | Irrelevant anonymous wrote : | 3> Avoid the DLQ. | If you don't want it to infinitely loop on the same error, then you need a DLQ or some other mechanism to avoid JMS trying to redeliver after the rollback/nack. e.g. redelivery delay in JBossMQ. If this hasn't at least 100 times before in this forum, I am a "monkey's uncle". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918439#3918439 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3918439 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
