Custom DLQ not a problem. I got that set that up. The thing that brought me onto the EJBException/RuntimeException is that the message was not retried until I added the container-tranaction bits to the MDB ejb-jar.xml. According to Adrian/JMS spec, throwing RuntimeExceptions from onMessage is not allowed, but from what I gather it is done quite a lot in practice. Anyway, retries work if I include the container-transaction stuff in the assembly descriptor.
Not sure I get the smarter enveloping stuff, am I missing something? If the MDB receives the jms message, successfully sends the mail to some recipients and then throws a runtimeexception the jms message ends up back on the original queue, and is retried by jms. When retried it should only send to the recipients that failed, so we need to keep track of who succeeded/falied somehow. But from my initial investigations it does not seem to be possible to modify the stuff stored in the jms message body, headers or properties from the jms listener/MDB. And since retries are handled by JMS, the sender doesn't get access to change anything either? Also, it doesn't seem to be possible to delay retries. I'll investigate some more, but if you have answers please shed some light! If not, I think the alternative mechanism outlined should do the job, but is seems like a slightly roundabout way of doing stuff. Kab View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3832823#3832823 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3832823 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
