[
http://issues.apache.org/jira/browse/JAMES-708?page=comments#action_12451128 ]
Robert Burrell Donkin commented on JAMES-708:
---------------------------------------------
The log enabling patch gives more information:
19/11/06 07:57:53 DEBUG imapserver: Calling reset() default Worker #4
19/11/06 08:01:48 DEBUG imapserver: Watchdog default Worker #4 has time to
sleep 300000
19/11/06 08:02:53 DEBUG imapserver: Error reading from stream
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.net.SocketInputStream.read(SocketInputStream.java:182)
at
org.apache.james.imapserver.debug.CopyInputStream.read(CopyInputStream.java:30)
at
org.apache.james.imapserver.ImapRequestLineReader.nextChar(ImapRequestLineReader.java:89)
at
org.apache.james.imapserver.ImapRequestHandler.handleRequest(ImapRequestHandler.java:68)
at
org.apache.james.imapserver.ImapHandler.handleNextRequest(ImapHandler.java:297)
at
org.apache.james.imapserver.ImapHandler.handleConnection(ImapHandler.java:244)
at
org.apache.james.util.connection.ServerConnection$ClientConnectionRunner.run(ServerConnection.java:468)
at
org.apache.excalibur.thread.impl.ExecutableRunnable.execute(ExecutableRunnable.java:55)
at
org.apache.excalibur.thread.impl.WorkerThread.run(WorkerThread.java:116)
19/11/06 08:02:53 INFO imapserver: Cannot handling request:
org.apache.james.imapserver.ProtocolException: Error reading from stream.
at
org.apache.james.imapserver.ImapRequestLineReader.nextChar(ImapRequestLineReader.java:96)
at
org.apache.james.imapserver.ImapRequestHandler.handleRequest(ImapRequestHandler.java:68)
at
org.apache.james.imapserver.ImapHandler.handleNextRequest(ImapHandler.java:297)
at
org.apache.james.imapserver.ImapHandler.handleConnection(ImapHandler.java:244)
at
org.apache.james.util.connection.ServerConnection$ClientConnectionRunner.run(ServerConnection.java:468)
at
org.apache.excalibur.thread.impl.ExecutableRunnable.execute(ExecutableRunnable.java:55)
at
org.apache.excalibur.thread.impl.WorkerThread.run(WorkerThread.java:116)
19/11/06 08:02:53 WARN imapserver: Stopping watchdog after handling last
request
19/11/06 08:02:53 DEBUG imapserver: Calling stop() default Worker #4
The issue doesn't seem positively harmful but is annoying and reduces
usability. IIRC IMAP specifies a long minimum auto-timeout. Wonder whether the
socket's timeout is too low for IMAP compliance.
> 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
>
> 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]
