Discussion:
DO NOT REPLY [Bug 18771] - FtpClient.retrieveFileStream returns null
b***@apache.org
2003-04-08 00:03:41 UTC
Permalink
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18771>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18771

FtpClient.retrieveFileStream returns null

***@apache.org changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED



------- Additional Comments From ***@apache.org 2003-04-08 00:03 -------
This is clearly a server side or a programming error and not an FTPClient
problem. As clearly explained in the documentation, if a data connection
cannot be established with the server, retrieveFileStream() will return null.
There is no way for us to reproduce your problem. Please trace the FTP
communication exchange with your server using the examples.PrintCommandListener
class from src/java/examples and provide the trace (with passwords removed)
as well as the program producing the problem. It is important for your or
provide the program, because given your description of the problem, it is
very likely that you are not calling completePendingCommand() after each file
transfer as required (and explained in the documentation and demonstrated
in the example programs).
b***@apache.org
2003-04-08 11:52:18 UTC
Permalink
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18771>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18771

FtpClient.retrieveFileStream returns null

***@itv.globalrefund.com changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |WORKSFORME



------- Additional Comments From ***@itv.globalrefund.com 2003-04-08 11:52 -------
oops, you are of course right, completePendingCommand() was not called.

So this was definitely my fault and is not a bug, sorry for that.

But maybe this should be changed to an improvement request.

It is not very convenient when FTPClient.retrieveFileStream returns null for an
existing file, just because the previous transfer was not terminated correctly
with completePendingCommand(). It would be great if FTPClient could check this
condition and issue a completePendingCommand() (or whatever is necessary to
make it work) internally when FTPClient.retrieveFileStream is called.
Loading...