mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Kuker (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SSHD-123) TcpipForward race condition & deadlock on client disconnect.
Date Thu, 21 Apr 2011 13:04:05 GMT
TcpipForward race condition & deadlock on client disconnect.
------------------------------------------------------------

                 Key: SSHD-123
                 URL: https://issues.apache.org/jira/browse/SSHD-123
             Project: MINA SSHD
          Issue Type: Bug
    Affects Versions: 0.5.0, 0.3.0, 0.6.0
         Environment: I am able to reproduce this every single time on my quad core windows
7 machine.
            Reporter: Bill Kuker


If a client with an active remote port forward disconnects at about the same time a new connection
comes in to that port forward two NioProcessor threads end up deadlocked in TcpipForwardSupport,
at the following spots:

NioProcessor-14 stuck at org.apache.sshd.server.session.TcpipForwardSupport.sessionCreated(...):
OpenFuture future = channel.open().await();

NioProcessor-2 stuck at org.apache.sshd.server.session.TcpipForwardSupport.close():
acceptor.dispose();

It appears that the new connection to the port forward is trying to create a new channel over
a session that is currently trying to close. Both threads end up waiting on different objects,
and are never notified.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message