[
https://issues.apache.org/jira/browse/SSHD-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201748#comment-16201748
]
Fulvio Cavarretta commented on SSHD-776:
----------------------------------------
Going back to what to do about messages going to channels that does not exists,
I fully agree with you that we should ignore *all* such messages.
I also would like to add another consideration: reasons for closing/shutting
down the ssh session (holding the logical channels) are a very *few* (and
anyway related to lower layers problems), like a problem at socket/transport
layer (the socket have been unexpectedly closed, or the transport get a
corrupted packet).
I think that by no mean the session should be shut down in other cases, because
it brings to all logical channels to be closed, stopping all active transfers.
To me it seems that current exception management is such that an error on a
channel or an error on the external connection (eg. the external FTP server in
our environment) easily lead to ssh session close, which, to me, seems a
drastic behavior ...
> 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
> Assignee: Goldstein Lyor
> Labels: channel, eof, forwarding, sshd
> Fix For: 1.7.0
>
> Attachments: dmzagent-1.7.0-snapshot.trc,
> dmzagent-WriteAbortException.trc, dmzagent.trc, dmzagent.trc.2,
> sshd.SSHD-776.patch
>
>
> 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)
