You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Goldstein Lyor (JIRA)" <ji...@apache.org> on 2019/04/30 13:15:00 UTC
[jira] [Resolved] (SSHD-911) Deadlock in Apache SshClient used for
local port forwarding
[ https://issues.apache.org/jira/browse/SSHD-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Goldstein Lyor resolved SSHD-911.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
[~roberto.deandrea] Marking this issue as fixed - let's continue the discussion regarding the 2nd deadlock in SSHD-912 which I have opened specifically for it.
> Deadlock in Apache SshClient used for local port forwarding
> -----------------------------------------------------------
>
> Key: SSHD-911
> URL: https://issues.apache.org/jira/browse/SSHD-911
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Roberto Deandrea
> Assignee: Goldstein Lyor
> Priority: Major
> Fix For: 2.3.0
>
> Attachments: spxp.usrdump.20382184@AIX72.DMZ.20190417205240026.log, spxp.usrdump.33095980@AIX72.DMZ.20190423123751496.log
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Hi Lyor,
> We have an Apache SSHD 2.2.0 client and server SSH pair used for local port forwarding of different protocols.
> In our lab environment we found that sometimes when the SSH client for any reason is disconnecting from the SSH server, a DEADLOCK happens on the sshClient regarding the threads in the thread pool.
> We are using builtin nio2 implementation for our SshClient.
> The deadlock is regarding the ClientChannelPendingMessagesQueue class added to fix routing problems for local port forwarding in the past.
> Attached you can find the thread dump taken after the deadlock happend.
>
> Can you please troubleshoot this problem ?
> [^spxp.usrdump.20382184@AIX72.DMZ.20190417205240026.log]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)