Perhaps you should read the docs for the connect() method closely. If you look closely at the error message (and read its docs), I think you'll find that it thinks you're trying to connect to a host whose name or IP address is "ftp://220.127.116.11/store/". So most likely you are only supposed to give connect() the host, not the entire URL.
Is it to do with the use of IP instead of a server name? What is way out if I still want to use the IP address?
Please someone help me.
do not use commons.net use ftp4j instead because while uploading a file using commons.net the file gets corrupted , i have this problem while i was developing the ftp client so
if you dont change the library now surely you will get a hell lot of pain in your neck.
my guess is that the problems were caused by user error.
but some one here itself told me that commons.net has a problem in uploading and the after changing just a library the same code runs without this uploading problem
Okay, fair enough.
@Mutua: You should of course investigate for yourself and draw your own conclusions, but just keep in mind if you have problems with data corruption, that is has been mentioned that this library may have that problem.
naved momin wrote:but some one here itself told me that commons.net has a problem in uploading and the after changing just a library the same code runs without this uploading problem
This is the sort of rubbish which people, unfortunately, actually base their decisions on. Please don't post rumours like this without providing information to support them.
My company has been using Commons.net code to do FTP transfers for several years now. So my belief is that those "problems in uploading" are, as already suggested, based on errors made by programmers using the product incorrectly.