Hi All, I have a servlet that runs under Tomcat which once a minute calls another servlet to retrieve email from a mail server, using the dispatch manager: // strDispatch is the email servlet name RequestDispatcher rd = request.getRequestDispatcher(strDispatch); rd.include(request, response);
If there are messages waiting on the server before Tomcat starts, the following chain of events occurs: 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 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 Minute 3: Default user is logged into mail server. See that messages are waiting. Invoke second sevlet and process messages normally. The locking in Minute 2 sometimes happens more than once before normal processing happens in each subsequent minute. If there are no messages waiting on the mail server before Tomcat starts, everything works normally with no exceptions. So, there are two problems here, the UnavailableException in Minute 1 and the AuthenticationFailedException in Minute 2. I ran this same code for months on Tomcat 3.1, then 4.0.3 with no problems. Can anyone tell me what happened between Tomcat 4.0.3 and 4.0.6 to make these exceptions occur and what I can do to fix them? I am using the versions of activation.jar and mail.jar that came with the Tomcat4.0.6 distribution, JDK1.3.1 and Win2KPro. Thanks very much for any help, Leona Slepetis -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
