My uploads are timing out, but only on my PC not others

[ucapsystem]

Hello,

This is my first time here. I know little to nothing about Java, but I know how to follow direction and I appreciate any help anyone gives!

I currently use a document manager web software program called
Omnistar Drive that utilizes JFileUpload Version 2.0

On my home network, I have a 30mb dl internet connection, a linksys wrt54g router, connected to two PCs (1 vista 64bit, 1 xp sp3) and 1 laptop (windows vista 32bit).

It does not matter which machine I use, when I try to upload the files I need to , which are typically anywhere inbetween 20-55mb a piece, the connection times out within the first 3-10 chunks.
Here is the the text from the console:

Java Plug-in 1.6.0_12
Using JRE version 1.6.0_12 Java HotSpot(TM) Client VM
User home directory = C:\Users\Chad
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
----------------------------------------------------


Feb 16, 2009 8:30:45 PM jfileupload.upload.client.MApplet <init>
INFO: JFileUpload 2.0 Build FINAL.001
Feb 16, 2009 8:30:45 PM jfileupload.transfer.client.http.HTTPTransfer autoDetectProxy
INFO: Auto-detect proxy settings : host = null
Feb 16, 2009 8:30:45 PM jfileupload.transfer.client.http.HTTPTransfer autoDetectProxy
INFO: Auto-detect proxy settings : port = -1
Feb 16, 2009 8:30:49 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split triggered
Feb 16, 2009 8:30:49 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 1/40
Feb 16, 2009 8:30:49 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 1/40
Feb 16, 2009 8:30:49 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:30:57 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:30:57 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:30:57 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:30:57 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 2/40
Feb 16, 2009 8:30:57 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 2/40
Feb 16, 2009 8:30:57 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:31:02 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:31:02 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:31:02 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:31:02 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 3/40
Feb 16, 2009 8:31:02 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 3/40
Feb 16, 2009 8:31:02 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:31:08 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:31:08 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:31:08 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:31:08 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 4/40
Feb 16, 2009 8:31:08 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 4/40
Feb 16, 2009 8:31:08 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:31:13 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:31:13 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:31:13 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:31:13 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 5/40
Feb 16, 2009 8:31:13 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 5/40
Feb 16, 2009 8:31:13 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:31:18 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:31:18 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:31:18 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:31:18 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 6/40
Feb 16, 2009 8:31:18 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 6/40
Feb 16, 2009 8:31:18 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:31:25 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:31:25 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:31:25 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:31:25 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 7/40
Feb 16, 2009 8:31:25 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 7/40
Feb 16, 2009 8:31:25 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:31:31 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:31:31 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:31:31 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:31:31 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 8/40
Feb 16, 2009 8:31:31 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 8/40
Feb 16, 2009 8:31:31 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:31:38 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:31:38 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:31:38 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:31:38 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 9/40
Feb 16, 2009 8:31:38 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 9/40
Feb 16, 2009 8:31:38 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:31:43 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:31:43 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:31:43 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:31:43 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 10/40
Feb 16, 2009 8:31:43 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 10/40
Feb 16, 2009 8:31:43 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:31:50 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:31:50 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:31:50 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:31:50 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 11/40
Feb 16, 2009 8:31:50 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 11/40
Feb 16, 2009 8:31:50 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:31:56 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:31:56 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:31:56 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:31:56 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 12/40
Feb 16, 2009 8:31:56 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 12/40
Feb 16, 2009 8:31:56 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:32:01 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload Status code = 200
Feb 16, 2009 8:32:01 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Feb 16, 2009 8:32:01 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload completed
Feb 16, 2009 8:32:01 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split started 13/40
Feb 16, 2009 8:32:01 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
INFO: Split completed 13/40
Feb 16, 2009 8:32:01 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
INFO: Upload (POST) started : C:\Users\Chad\Desktop\audits_feb_1_2_zipped\turningpointdebtsettlement.zip
Feb 16, 2009 8:32:22 PM jfileupload.transfer.client.http.HTTPUploadTransfer transfer
SEVERE: java.net.ConnectException: Connection timed out: connect
Feb 16, 2009 8:32:22 PM jfileupload.transfer.client.http.HTTPUploadTransfer splitAndTransfer
SEVERE: jfileupload.transfer.client.core.ClientException: java.net.ConnectException: Connection timed out: connect
Feb 16, 2009 8:32:22 PM jfileupload.transfer.client.http.HTTPUploadTransfer run
INFO: Upload failed

Furthermore, when I go to a friends house, the files upload just fine. I have contacted both my ISP and Lynksys as well as Omnistar to no prevail. Can anyone shed some light on this issue?

[support]

If it's a server-side issue then you could try to enable "retry" parameter. It allows to retry failed upload several times, for instance:
<PARAM NAME="retry" VALUE="5">
However, as JFileUpload is integrated into another product, I'm not sure you have access to applet parameters.

If it's a a client-side issue, then do you have a personal firewall ?

[ucapsystem]

What is the name of the file to edit? I can also edit anything in the mysql database as well as server files.

On my end..

I have tried 3 different machines. Disabled all anti-virus and firewall. The xp machine doesnt even have anything.

I can walk in here with my laptop, connect wirelessly and fail to upload.

Go to a friends house and it uploads fine. However, my bandwith is FAR greater then his.
I have contacted Comcast, Linksys, Tried browsers, updated java, operating systems. Im stumped.

[support]

The file to update is applet_http.js. Do you have this one ?

[ucapsystem]

No, and the software manufacture says that everything is client side and they dont have any files that I dont.

Here is the files in the js directory

disable.js
editor.js
form.js
getbrowser.js
helptip.js
jupload.jar
layertools.js
onload.js
popcalender.js
popus.js
htmlarea(folder)

In the lib folder

batchui.jar
chttpclient.jar
clogging.jar
cnet.jar
ftpimpl.kar
httpimpl.jar
jfileupload.jar
lang.php
previewui.jar


If the file IS in one of these .jar files, please also tell me how to extract them in the next responce, as our replies our a day apart and I want as much info as I can get at once.

[ucapsystem]

Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

To me this is the underlining problem.

the only thing I can think of is that the error has to be caused by reply packets being delivered wrong or not at all.

Thats why I thought it was a router issue. But I tried wiring directly to the modem same problem. And remember, I can take my laptop to a friends house and it uploads PERFECTLY. As soon as I get home I have a problem.

[support]

No, this is a simple warning that cannot explain time out issue. Also, the parameter should be in a .js or in a .php not under a .jar file. Search for 'applet' in these files.

Finally, I would like you to try our online demo and upload some files to see if you have the time out issue too: http://www.jfileupload.com/products/dem ... _http.html

[ucapsystem]

Which files specifically.

Your not asking me to search every php file on the server are you?
The files I listed were all .js files, no php files.

The demo worked fine, which I also explained to OmniStarInteractive.

[support]

Well, I don't know how they bundled our applet so I don't know which file. All I can say is that all applet parameters are under <APPLET> tag. In our product, it's under applet_http.js. Make search in all the .js you have, it may be under form.js.

[ucapsystem]

It is not in ANY of the .js files