mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashank (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SSHD-108) Add upload monitoring to sftp
Date Tue, 07 Jun 2016 11:24:21 GMT

    [ https://issues.apache.org/jira/browse/SSHD-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318313#comment-15318313

Shashank commented on SSHD-108:

[~lgoldstein] Thanks, it worked..

May be one last question, I have developed an independent application which works fine with
above functionality. When this independent application is integrated into main application
I see following issue,

Whenever a client tries to acquire a connection. Initial key exchange happens through socket.
After this, when tried to read from the socket for the second time for authentication information,
nothing is read from the socket and after sometime (~2mins) following exception message is
being thrown and connection is being closed.

"IOException: The specified network name is no longer available."

I have noticed that when key exchange information is read from socket, socket buffer limit
got reduced to less size from the default initialization limit value. Where as while trying
to read for the second time (For authentication information) socket buffer size does not get
reduced but remains as default initialization value and nothing happens since then. 

Do you have any idea why this behavior is seen?

> Add upload monitoring to sftp
> -----------------------------
>                 Key: SSHD-108
>                 URL: https://issues.apache.org/jira/browse/SSHD-108
>             Project: MINA SSHD
>          Issue Type: Improvement
>    Affects Versions: 0.5.0
>            Reporter: Richard Evans
>            Assignee: Goldstein Lyor
>            Priority: Minor
>             Fix For: 1.1.0
> We have sshd integrated into our application and sftp is working fine.  One of the requirements
is to initiate some action when a file upload it complete.  I have made this work by implementing
handleClose in my SshFile implementation and performing the action if createOutputStream had
been called previously.  This seems a bit ugly though; it might be nicer if there was some
plug in mechanism to monitor file transfers.
> Ideally the monitor would be able to distinguish between a successful upload and a cancelled
one (via ctrl-c at the client), but a quick perusal of the sftp stuff seems to inidicate that
this is not possible. 

This message was sent by Atlassian JIRA

View raw message