[
https://issues.apache.org/jira/browse/SSHD-911?focusedWorklogId=230646&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-230646
]
ASF GitHub Bot logged work on SSHD-911:
---------------------------------------
Author: ASF GitHub Bot
Created on: 22/Apr/19 10:17
Start Date: 22/Apr/19 10:17
Worklog Time Spent: 10m
Work Description: lgoldstein commented on pull request #101: [SSHD-911]
Check if client session/channel is open before writing a message through
ClientChannelPendingMessagesQueue
URL: https://github.com/apache/mina-sshd/pull/101
Doesn't really explain the deadlock, but should mitigate it under the
circumstances described in the issue
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 230646)
Time Spent: 10m
Remaining Estimate: 0h
> 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]
>
> 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)
