In addition to ensuring that subcribers of topics are durable, the quick answer is to ensure the handler of the message is enrolled in a Tx and rolls back on exception. JMS uses a data source, so you may want to ensure the data source is XA, as we do.
The question is what do you do when you have to roll back message handling due to a temporary problem (remote connectivity issue,) and you want to ensure continued message delivery until the external problem is corrected, similar to how SMTP engines usually handle bounces today. I'm working on a proposal for a workaround to issues that I'll post to get peer review here. I'd really love to know how others are solving this problem. If there is an easy solution, I'd sure like to know what it is before we implement a complex workaround. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919640#3919640 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919640 ------------------------------------------------------- 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
