[jira] Updated: (NET-327) "Unconnected sockets not implemented" when using FTPSClient

2011-03-10 Thread Bogdan Drozdowski (JIRA)

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

Bogdan Drozdowski updated NET-327:
--

Attachment: ftps-reconn.diff

A code sample would be nice. But I've managed to do my own: executing the 
sequence "connect, execPROT(P), login, disconnect" twice on the same client 
instance causes the error. My patch fixes this issue - it overrides the 
disconnect() method of FTPClient in FTPSClient to re-set the SocketFactories 
(null is allowed, because the SocketClient knows how to deal with it). Thanks 
goes to Bengt Rodehav 
(http://www.mail-archive.com/user@commons.apache.org/msg04935.html) for 
pointing this out.

> "Unconnected sockets not implemented" when using FTPSClient
> ---
>
> Key: NET-327
> URL: https://issues.apache.org/jira/browse/NET-327
> 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
> 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: http://www.mail-archive.com/user@commons.apache.org/msg04933.html
> and http://www.mail-archive.com/users@camel.apache.org/msg08732.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] Updated: (NET-327) "Unconnected sockets not implemented" when using FTPSClient

2010-07-11 Thread Sebb (JIRA)

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

Sebb updated NET-327:
-

Component/s: FTP

> "Unconnected sockets not implemented" when using FTPSClient
> ---
>
> Key: NET-327
> URL: https://issues.apache.org/jira/browse/NET-327
> 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
>
> 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: http://www.mail-archive.com/u...@commons.apache.org/msg04933.html
> and http://www.mail-archive.com/us...@camel.apache.org/msg08732.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.