Hi all,

we just switched to MINAin JAMES same weeks ago. Sometimes I see the
following exception:


ERROR 09:42:24,637 | james.smtpserver | Caught exception:
HeapBuffer[pos=0 lim=36 cap=64: 34 35 31 20 55 6E 61 62 6C 65 20 74 6F
20 70 72...]
org.apache.mina.core.write.WriteToClosedSessionException
        at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.clearWriteRequestQueue(AbstractPollingIoProcessor.java:573)
        at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.removeNow(AbstractPollingIoProcessor.java:534)
        at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.removeSessions(AbstractPollingIoProcessor.java:497)
        at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.access$600(AbstractPollingIoProcessor.java:61)
        at 
org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:974)
        at 
org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)


I think it happen when we try to write out something to the client
back but the session was already closed. We usually call
IoSession.isConnected() before write stuff, so how could this happen ?
I think its not really critical but having this stuff in the log is a
bit annoying.

Bye,
Norman

Reply via email to