[ http://issues.apache.org/jira/browse/JAMES-708?page=comments#action_12451411 ] Robert Burrell Donkin commented on JAMES-708: ---------------------------------------------
I've been running my local fork (pre-710) for a few hours with the connection timeout set to 0. No reoccurence as yet. Gut feeling tells me it's the timeout that's the issue so you can hold off that thinking for a while ;-) Will report back later this week once I have more evidence > 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]
