[ http://issues.apache.org/jira/browse/JAMES-708?page=comments#action_12451458 ] Robert Burrell Donkin commented on JAMES-708: ---------------------------------------------
The local fork with 710 seems stable with a long timeout. With a short timeout, the client is effectively unusable but no errors :-/ Haven't had the original issue yet with 710 but IMAP is not stable for me without the timeout at least that stated in the spec. May try per handler configuration later this week. > 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]
