[
https://issues.apache.org/jira/browse/SSHD-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191207#comment-16191207
]
Goldstein Lyor commented on SSHD-776:
-------------------------------------
P.S. regarding proper channel close procedure - I re-read the section you
mentioned, and I can see how someone would interpret it the way you do - that's
why I initiated the same change :) to the code that handles EOF that you did.
Now that I have re-read it, it does not seem to describe what is the exact
procedure to handle EOF after CLOSE, so I feel fine tolerating it.
> 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
> Priority: Blocker
> Attachments: dmzagent.trc, 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)
