You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2013/07/23 12:10:50 UTC
[jira] [Resolved] (SSHD-178) Possible deadlock in client when
getting SSH_MSG_DISCONNECT on invalid channel
[ https://issues.apache.org/jira/browse/SSHD-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved SSHD-178.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.9.0
Assignee: Guillaume Nodet
> Possible deadlock in client when getting SSH_MSG_DISCONNECT on invalid channel
> ------------------------------------------------------------------------------
>
> Key: SSHD-178
> URL: https://issues.apache.org/jira/browse/SSHD-178
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 0.7.0
> Environment: java version "1.7.0_05"
> OpenJDK Runtime Environment (IcedTea7 2.2.1) (Gentoo build 1.7.0_05-b21)
> OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
> Reporter: Alon Bar-Lev
> Assignee: Guillaume Nodet
> Fix For: 0.9.0
>
>
> In some cases the channel closes before the last message is sent (or so I understand from the log)
> I can reproduce this easily when running very short commands.
> ---
> 6265 [NioProcessor-20] INFO org.apache.sshd.client.channel.ChannelExec - Send SSH_MSG_CHANNEL_REQUEST exec
> 6373 [NioProcessor-20] INFO org.apache.sshd.client.channel.ChannelExec - Received SSH_MSG_CHANNEL_REQUEST on channel 0
> 6374 [main] INFO org.apache.sshd.client.channel.ChannelExec - Send SSH_MSG_CHANNEL_OPEN on channel 1
> 7374 [NioProcessor-20] INFO org.apache.sshd.client.session.ClientSessionImpl - Received SSH_MSG_DISCONNECT (reason=2, msg=Received data for nonexistent channel 0.)
> ---
> When getting this SSH_MSG_DISCONNECT message the client is timed out waiting for CLOSED/EOF.
> Not sure where the problem is, but it seems like the client is closed and the program is not notified, or the message on the closed channel alter the behaviour.
> If add some debug messages it happens less frequent, so I guess this is race/synchronization issue.
> I will happy to provide any additional required information.
--
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