I have a third-party app (IOW, not my code) that uses a message driven bean to send emails. I'm running it in Weblogic 6.1. Any time the onMessage() method of the MDB fails, it wraps any resulting exception in an EJBException and throws the EJBException.
What happens next is that Weblogic will discard the MDB (per the EJB 2.0 spec), and then create a new MDB instance and retry the call to onMessage(). This cycle continues as long as the onMessage() call keeps failing, and this can result in an endless cycle which fills the log files, or in some cases sends thousands of email messages until the server is killed. I'm not all that familiar with MDB, and I haven't found anything in the EJB 2.0 spec or in the Weblogic 6.1 docs that specifies that the container will retry onMessage() calls that fail. Can anyone provide any insight into this? How can I get the container to simply give up when an onMessage() call fails? Is this a Weblogic-specific behavior for which there is some configuration setting I can change? __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
