[
https://issues.apache.org/jira/browse/SSHD-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190996#comment-16190996
]
Fulvio Cavarretta commented on SSHD-776:
----------------------------------------
Hi [~lgoldstein] thanks for you quick replay, sorry if my explanation has not
been clear.
In our environment we use a single SSH pipe where all connections to external
FTP servers are multiplexed inside different channels. To support PASV FTP
command, a new fowarding channel is opened/closed in the SSH pipe, to let our
FTP client to open the data connection to external server.
We have multiple clients opening/closing a logical channel inside the same SSH
pipe in a multithread environment.
We did some further investigations and it seems that a certain point inside
SSHD there is the follwing exception (line 20120 file _dmzagent.trc_):
_SshException: Received SSH_MSG_CHANNEL_EOF on unknown channel 24_
>From out investigation it seems that when SSH_MSG_CHANNEL_EOF has been
>received, that channel has already being destroyed.
After that exception, the SSH pipe does not manage any other message from the
remote endpoint (like managing the SSH_MSG_IGNORE that we sent to let the
connection alive, so that the connection expires for idel timeout).
> SSHD local port forwarding close session unexpectedly
> -----------------------------------------------------
>
> Key: SSHD-776
> URL: https://issues.apache.org/jira/browse/SSHD-776
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Fulvio Cavarretta
> Priority: Blocker
> Attachments: dmzagent.trc.2
>
>
> Apache SSHD used in local port forwarding mode.
> A client is connecting to a remote FTP server through Apache SSHD via a
> custom software.
> When a new logical channel inside a single SSHD session get an IO error (e.g.
> the remote destination close the connection suddenly, the whole session is
> shut down causing all other logical channel to be closed (see line 8861of
> attached trace file).
> It seems like the _exceptionCaught_ mathod should not be called in this case
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
