[
https://issues.apache.org/jira/browse/SSHD-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191349#comment-16191349
]
Goldstein Lyor commented on SSHD-776:
-------------------------------------
After giving a quick glance over the latest stack traces you sent I am not sure
we are concentrating on the right flow - perhaps we should be asking why is it
that closing the channel (and ignoring the EOF) also closes the session when
obviously it shouldn't ? Can it be that your use of the client code does not
keep it open ? Can you attach some code sample as to how you are using the SSHD
client-side code ?
> 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)
