Our Products:   CompleteFTP  edtFTPnet/Free  edtFTPnet/PRO  edtFTPj/Free  edtFTPj/PRO
0 votes
10.1k views
in Java FTP by (440 points)
I got strange problems with one ftp-server.
I use edtftpj in my application to upload some files.
The problem:
Very often, I don't know when exactly, it seems that there is no connection any more or so.
im passive mode the log is printing -->pasv continuesly
in active mode it's printing -->port "strange ip's starting with 0.0.x.x" continuesly

I mailed the administrator of the server, as this problem does not occur on a different server and also not on my local ftp-server
but he can't help me.
The strange thing is that it occurs sometimes (often) but not always.
Is anything known about that? Maby any special setup required or so?

Thanks for your help

Frank

15 Answers

0 votes
by (440 points)
Yes i will write a test program.
To which adress should I send it?
0 votes
by (51.6k points)
please send it to support[at]our-domain

- Hans (EDT)
0 votes
by (440 points)
Now I don't underdstand anything anymoe....
In the Test Program (with connect , dir and then quit)
the error is "unexpected null reply received"
can this be catched?

But I really don't understand, because in the main application there is also
only one class which deals with ftpj and the code for ftp is that, that I posted.
Maybe it's a swing internal thing thing, which I don't understand,
the class is a subclass of JInternalFrame with a progressBar inside
in the constructor i do some setup and add the progreesbar and then call connect()
the code of connect() is the one I posted.....this maybe the error: calling connect from the constrcuctor

Ok, as I planned to change the gui from "DesktopFrame-sytle" to another ,an setting the progressbar to a fix location somewhere and not in an InternlaFrame which is build just before connecting to ftp, maybe the error is away, I will tell you when I've done so.

I guess for the "null reply" you have a solution, where to catch it the best

Thanks for your help
0 votes
by (162k points)
Make sure you have version 1.5.2, the latest one.
0 votes
by (440 points)
I have 1.5.2

i guess i can catch it with

catch(Exception e)
{
//couldn't connect//
}

Categories

...