[
https://issues.apache.org/jira/browse/IMAP-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011624#comment-13011624
]
Wojtek Strzalka commented on IMAP-270:
--------------------------------------
the exceptions are:
-------------------------------------
Mar 26, 2011 4:51:21 AM org.jboss.netty.channel.SimpleChannelUpstreamHandler
WARNING: EXCEPTION, please implement
org.apache.james.imapserver.netty.ImapChannelUpstreamHandler.exceptionCaught()
for proper handling.
java.nio.channels.ClosedChannelException
at
org.jboss.netty.channel.socket.nio.NioWorker.cleanUpWriteBuffer(NioWorker.java:637)
at
org.jboss.netty.channel.socket.nio.NioWorker.writeFromUserCode(NioWorker.java:370)
..........................
java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcher.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
at sun.nio.ch.IOUtil.write(IOUtil.java:60)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
...................
----------------------------------
repeated really many times with long stacks.
We should probably handle it more smoothly
> Stack traces in log file on unexpected client disconnect
> --------------------------------------------------------
>
> Key: IMAP-270
> URL: https://issues.apache.org/jira/browse/IMAP-270
> Project: JAMES Imap
> Issue Type: Improvement
> Reporter: Wojtek Strzalka
>
> In case client will drop in some circumstances excessive log is created with
> plenty of stack traces.
--
This message is automatically generated by JIRA.
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]
