JFileUpload slow

[PilsDieb]

Hi,
I am using JFileUpload for an FTP connection to an proftpd with PASV mode.
Now on some windows environments (not all) it uploads files much slower than filezilla e.g. with the same settings. On other systems (mostly linux, but even some windows), it is as fast as other ftp clients. The speed on normal systems is ~5MB/s, the slow is ~200KB/s. Both Testsystems use the same internetconnection.

Is this a known problem?
Do you know a solution to get the expected upload speed in all environments?

I appreciate your help
PilsDieb

[support]

No, not known problem.
Could you check/compare JRE versions on computers where it's slow and normal.

[PilsDieb]

Hi again and thanks for your quick reply.
Now I have found out, that jfileupload behaves a little bit different than other clients regarding the passive mode:
It sends the PASV command BEFORE the USER and PASS, which does filezilla e.g. AFTER USER and PASS. And in the jfileupload-log there is no response to the PASV command which should look like 227 Entering Passive Mode (XX,XX,XX,XX,XX,XX). where XX are some numbers.

I pasted an anonymised log from jfileupload.
Is there an option with wich I can delay the PASV command ?

Edit: here are the used parameters (seems usual)
<PARAM NAME="param1" VALUE="username">
<PARAM NAME="value1" VALUE="[USERNAME]">
<PARAM NAME="param2" VALUE="password">
<PARAM NAME="value2" VALUE="[PASSWORD]">
<PARAM NAME="param3" VALUE="pasv">
<PARAM NAME="value3" VALUE="true">

There are some more (forward, folderdepth, whitelist forwardparameters, maxfiles, mode=ftp) which I can post, if needed.

Thanks in advance
PilsDieb

Select or drag and drop file to upload
--------------------------------------------------
> CONNECT [HOST].pokerstrategy.com
< 220 ProFTPD 1.3.1 Server ([NAME]) [[IP]]
> PASV
> USER [USERNAME] PASS ******
< 230 Anonymous access granted, restrictions apply
Uploading : random.avi
(104.857.600 bytes)
Upload started ...> TYPE I
< 200 Type set to I
> LIST random.avi
< 450 random.avi: No such file or directory
> TYPE I
< 450 random.avi: No such file or directory
> STOR random.avi
> ABOR
< 226 Abort successful
Upload cancelled
--------------------------------------------------
> DISCONNECT

[PilsDieb]

UPDATE:
I did some more analysing and it seems the Protocol output in jfileupload is not what really happens, so the PASV command is sent correctly, I think. The only difference in protocol seems now to be a OPTS UTF8 ON command, that is sent by filezilla, but not by jfileupload. Even I cannot imagine, that this causes the speed difference, I would like this command to be sent by jfileupload. Is there an option to do this ?

Thanks in advance
PilsDieb

[support]

Could "OPTS UTF8 ON" be passed through FTP SITE command ? If so then try:
<PARAM NAME="param8" VALUE="sitecommand">
<PARAM NAME="value8" VALUE="OPTS UTF8 ON">

[PilsDieb]

Hi again,
no this is not an SITE command, but an own FTP command, so this would not help.
we still could not find a solution for this issue.
Beside this we encountered another problem:

For large files (>~1GB) the forward after the upload does not work. The applet remains in uploading state, though the file is completely uploaded. The server (proftpd) recognizes an transfer stalled timeout and disconnects, the applet still "waiting". We are using passive FTP because clients are usually behind a NATing router which shouldnt be reconfigured for using our FTPsite. I have activated sending NOOP commands every 60s, but this does not help.

Do you know a possibility with which we can solve this ?

Thanks in advance
PilsDieb

[support]

How did you enable periodic NOOP command ? through commandmonitor parameter ?

[PilsDieb]

yes

[support]

Are you able to increase command channel timeout on your FTP server ?

[PilsDieb]

yes, but that didnt help too.
Now we have changed the upload to http and this works for us.
But we are still experiencing the slow upload speed on windows clients, though we changed the protocol. It seems to occur only to amazon instances, only from windows machines and only with jfileupload.

Maybe you have heard about this problem from other users.

Thank you for your help
PilsDieb