[
https://issues.apache.org/jira/browse/SSHD-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16828047#comment-16828047
]
Goldstein Lyor commented on SSHD-911:
-------------------------------------
{quote}
With your suggested code changes the old deadlock seems definetely FIXED
{quote}
I am not so sure - it feels like all it does is minimize the chance of a
deadlock by changing the timing so your test suite probable isn't fast enough
or does not "score" the correct timing. I am not sure that the root cause (if
indeed there is a deadlock) has been fixed. Furthermore, seems like a bit of an
overhead to check if channel/session are open for each and every packet. Will
reflect on this some more...
{quote}
Can you please help me to fix this new deadlock ?
{quote}
I'll see what I can do.
> 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],
> [email protected]
>
> Time Spent: 10m
> 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 ?
> [^[email protected]]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
