Hi, So you didn't get any errors with 4.0.3 and now are getting them with 4.0.6?
Would you be willing to try 4.0.6-LE and JDK 1.4.1? >Minute 1: >Default user is logged into mail server. >See that messages are waiting. >Attempt to invoke second sevlet. >Exception is thrown: javax.servlet.UnavailableException: Cannot invoke >default servlet through invoker This doesn't seem to be a JavaMail exception. It's generally through that you can't programmatically invoke the default servlet. What is the argument (you called it strDispatch or something like that) to the RequestDispatcher? >Minute 2: >Default user is logged into mail server. >See that messages are waiting. >Attempt to nvoke second sevlet. >Exception is thrown: javax.mail.AuthenticationFailedException: Can't get >lock. Mailbox in use What happens if you catch this one and retry (once)? Can you pre-clear (or unlock) the mailbox before making this call? Alternatively, can you have a mail retriever of some sort that's NOT a servlet get the mail, and have the first servlet use this mail retriever, skipping the whole RequestDispatcher.include mechanism? I know this is not an answer ;) Just suggesting an alternative design that should be easy to implement... Yoav Shapira Millennium ChemInformatics -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
