You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Konrad Garus (JIRA)" <ji...@apache.org> on 2012/07/24 17:13:35 UTC
[jira] [Closed] (NET-476) FTP parser initialization from invalid
line
[ https://issues.apache.org/jira/browse/NET-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Garus closed NET-476.
----------------------------
Resolution: Fixed
> FTP parser initialization from invalid line
> -------------------------------------------
>
> Key: NET-476
> URL: https://issues.apache.org/jira/browse/NET-476
> Project: Commons Net
> Issue Type: Bug
> Components: FTP
> Affects Versions: 3.1
> Environment: Ubuntu Linux 10.04 amd64, vsftpd 2.2.2
> Reporter: Konrad Garus
>
> After upgrading from 1.4.1 to 3.1, we noticed the FTP client sometimes fails to list files. It seems to occur intermittently, possibly when the system is under relatively high load and does not respond immediately.
> From stacktraces, it seems like multithreading issues or trying to parse system type from reply to another command than SYST:
> {code}
> Caused by: org.apache.commons.net.ftp.parser.ParserInitializationException: Unknown parser type: PORT command successful. Consider using PASV.
> at org.apache.commons.net.ftp.parser.DefaultFTPFileEntryParserFactory.createFileEntryParser(DefaultFTPFileEntryParserFactory.java:118)
> at org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2359)
> at org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2142)
> at
> {code}
> {code}
> Caused by: org.apache.commons.net.ftp.parser.ParserInitializationException: Unknown parser type: Directory send OK.
> at org.apache.commons.net.ftp.parser.DefaultFTPFileEntryParserFactory.createFileEntryParser(DefaultFTPFileEntryParserFactory.java:118)
> at org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2359)
> at org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2142)
> at
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira