commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bogdan Drozdowski (JIRA)" <>
Subject [jira] Commented: (NET-327) "Unconnected sockets not implemented" when using FTPSClient
Date Fri, 11 Mar 2011 16:08:00 GMT


Bogdan Drozdowski commented on NET-327:

Bengt: yes, notify others and check if this fixes your problem (not just the sequence of commands
that I've found). About the release date: I'm not a project developer or leader, ask them.
Version 3.0, however, is marked as the "ssh release", so it may be not too soon, unfortunately.
On the other hand, bugfixing gained some speed recently, so the project isn't standing in
one point.

> "Unconnected sockets not implemented" when using FTPSClient
> -----------------------------------------------------------
>                 Key: NET-327
>                 URL:
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 2.0
>         Environment: Windows XP SP3, Java 1.6.0_18, Apache Karaf 1.6.0
>            Reporter: Bengt Rodehav
>             Fix For: 3.0
>         Attachments: ftps-reconn.diff
> I'm using Apache Camel as an integration platform. Specifically, at the moment, I depend
on the ftp/ftps/sftp support in the camel-ftp component. Under the hood Camel uses Commons
Net for ftp and ftps support.
> Recently, the camel-ftp component was enhanced (on my request) with the possibility to
use a secure data channel. This is accomplished by using the execProt() (and execPsbz()) method
in class FTPSClient.
> However, later on (in case Camel needs to reconnect), one of the connect() methods in
the base class to FTPSClient is called. Unfortunately all the connect methods first create
an unconnected socket and then tries to connect it. The connection factory now associated
with the FTPSClient then throws an exception stating: "Unconnected sockets not implemented".
> It seems like the FTPSClient does not support "re-connect" once it has entered secure
communications mode.
> See also:
> and

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message