[ http://issues.apache.org/jira/browse/JAMES-708?page=comments#action_12451661 ] Joachim Draeger commented on JAMES-708: ---------------------------------------
Imap should be configured with the required timeouts (30 min.) by default. The reference to the RFC in config.xml should be sufficient as a warning. Let's see if the patch for JAMES-713 gets accepted soon. If not, we need a solution to bumb up the socket timeout e.g. in ImapHandler.initHandler() > ImapHandler - unreachable code reached > -------------------------------------- > > Key: JAMES-708 > URL: http://issues.apache.org/jira/browse/JAMES-708 > Project: James > Issue Type: Bug > Components: IMAPServer > Affects Versions: Trunk > Reporter: Robert Burrell Donkin > Attachments: imap-timeout-warning.patch > > > Once in a while during normal operation, the client pops up a mysterious > error message (will post next time it happens) > When this happens, the log indicate that the code under this code: > theWatchdog.start(); > while ( handleNextRequest(remoteHost, remoteIP) ) { > if (!handlerIsUp) { > getLogger().debug("Handler has been resetted"); > return; > } > theWatchdog.reset(); > } > // TODO is this unreachable code because of !handlerIsUp -> > return? > getLogger().warn("Stopping watchdog after handling last request"); > theWatchdog.stop(); > > is reached contrary to the TODO > (Will add more logs and information) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
