[ 
https://issues.apache.org/jira/browse/SSHD-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821326#comment-16821326
 ] 

Goldstein Lyor commented on SSHD-911:
-------------------------------------

{quote}Can you please troubleshoot this problem ?{quote}
I'll see what I can do - it will take some time though... 

In any case, any additional information you can provide may prove helpful - 
e.g. can you try and focus some more when the "sometimes" occurs ? Is it often 
or rare ? Perhaps you can open some *selective* debug log levels and see what 
happens around the time that it seems to hang.

{quote}
The deadlock is regarding the ClientChannelPendingMessagesQueue class added to 
fix routing problems for local port forwarding in the past.
{quote}
Can you explain what leads you to believe that this class code is causing the 
problem ?

> 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
>         Attachments: [email protected]
>
>
> 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 ?
> [^[email protected]]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to