You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "James (JIRA)" <ji...@apache.org> on 2013/05/15 21:33:16 UTC
[jira] [Created] (DIRMINA-944) Server logs 'Connection reset by
peer' and sends RST but no disconnect found in packet capture
James created DIRMINA-944:
-----------------------------
Summary: Server logs 'Connection reset by peer' and sends RST but no disconnect found in packet capture
Key: DIRMINA-944
URL: https://issues.apache.org/jira/browse/DIRMINA-944
Project: MINA
Issue Type: Bug
Components: Transport
Affects Versions: 1.0.5
Environment: SUSE Linux Enterprise Server 11 SP 2
Reporter: James
Priority: Minor
Server is logging an exception with 'Connection reset by peer'. This is intermittant; usually a second connection attempt will work. However, in packet capture there is no difference between the two examples up to the point where the server sends an RST packet - there is definitely no reset from the client side.
This happens right after the server sends the SSL hello, when the next step should be key negotation.
I'm not sure what the next steps are to troubleshoot this or get more debug information.
13-05-15 10:19:18 [pool-3-thread-1538] WARN nio.FtpLoggingFilter: EXCEPTION :
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
at sun.nio.ch.IOUtil.read(IOUtil.java:171)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)
at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.j
ava:202)
at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.j
ava:42)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(Abstract
PollingIoProcessor.java:620)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(Abstr
actPollingIoProcessor.java:598)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(Abstr
actPollingIoProcessor.java:587)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(Ab
stractPollingIoProcessor.java:61)
at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run
(AbstractPollingIoProcessor.java:969)
at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnabl
e.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:662)
13-05-15 10:19:18 [pool-3-thread-1538] ERROR impl.DefaultFtpHandler: Exception c
aught, closing session
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
at sun.nio.ch.IOUtil.read(IOUtil.java:171)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)
at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.j
ava:202)
at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.j
ava:42)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(Abstract
PollingIoProcessor.java:620)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(Abstr
actPollingIoProcessor.java:598)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(Abstr
actPollingIoProcessor.java:587)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(Ab
stractPollingIoProcessor.java:61)
at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run
(AbstractPollingIoProcessor.java:969)
at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnabl
e.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:662)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira