[ 
https://issues.apache.org/jira/browse/SSHD-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fulvio Cavarretta updated SSHD-776:
-----------------------------------
    Attachment: dmzagent-WriteAbortException.trc

Hi [~lgoldstein], we integrated you modifications in the 1.6.0 codebase and 
recompilaed in our environment.

We also added a trace when the new _WriteAbortedException_ is set 

see. line 2165 in [^dmzagent-WriteAbortException.trc]

I could not understand why in _Nio2Session.doCloseImmediately_  _writes.poll()_ 
is not empty, but setting the exception lead the session to be closed.

Do you think that changing the code to:

{code}
    @Override
    protected void doCloseImmediately() {
        for (;;) {
            // Cancel pending requests informing them of the cancellation
            Nio2DefaultIoWriteFuture future = writes.poll();
            if (future != null) {
                log.warn("Write request aborted due to immediate session 
close");
                future.setWritten();
            } else {
                break;
            }
        }
...
{code}

can be possible solution ?


> 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)

Reply via email to