I've made a few changes for retry. I went with the alternative implementation I suggested since I got stuck with the JMS/DLQ stuff (Still not sure if it is possible). If a mail fails for remote/local delivery the MDB puts it in a wrapper object and calls JMSMailListener again.
The wrapper object keeps track of the number of retries, who to resend to etc. and JMSMailListener now generates the bounce messages. The config for JMSMailListener contains the retry intervals. You can set up how many times you want to retry, and configure the delays between the retries so you can have it try frequently in the beginning and then less frequently later. It might be a more roundabout way of doing it, but I think it is more flexible. If I have tagged cvs correctly, the changes should be between the following tags on the head branch: Kab_made_some_changes_for_retry (BEFORE) Kab_commited_some_changes_for_retry (AFTER) Cheers, Kab View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834706#3834706 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834706 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
