[
https://issues.apache.org/jira/browse/SSHD-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191336#comment-16191336
]
Goldstein Lyor commented on SSHD-776:
-------------------------------------
I am not sure this is a good idea - calling {{setWritten}} indicates to whoever
sent the request that the request was *successfully* written, which obviously
is not the case - it is *misleading*. While it may solve your immediate
problem, I am not comfortable with this erroneous report. I would prefer
investigating who is receiving the {{WriteAbortedException}} and why they
decide to close the session.
Furthermore:
{quote}
we integrated you modifications in the 1.6.0 codebase and recompilaed in our
environment.
{quote}
I do not recommend it - better to clone https://github.com/apache/mina-sshd/
and work from there since (a) it contains a few bug fixes and (b) any future
version release will be cut from this code base, so any changes/fixes we
introduce due to this issue will have to be compatible with it and not 1.6.0
> 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,
> dmzagent-WriteAbortException.trc
>
>
> 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)
