Community
Participate
Working Groups
What steps will reproduce the problem? 1. check for updates 2. confirmed updates 3. agreed -- Error Details -- Date: Thu Oct 21 13:38:18 GST 2010 Message: Transfer Exception Severity: Error Product: Eclipse 1.2.1.20090812-1036 (org.eclipse.epp.package.php.product) Plugin: org.eclipse.ecf.provider.filetransfer Session Data: eclipse.buildId=M20090917-0800 java.version=1.6.0_17 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.php.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.php.product Exception Stack Trace: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.apache.commons.httpclient.ContentLengthInputStream.read(ContentLengthInputStream.java:170) at java.io.FilterInputStream.read(Unknown Source) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:108) at java.io.FilterInputStream.read(Unknown Source) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:127) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:140) at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Does this relate to ECF?
(In reply to comment #1) > Does this relate to ECF? It sounds likely that in this environment the filetransfer read is blocking for long enough to timeout. It's possible to set the read and connect timeouts for the httpclient provider via system properties...i.e. make them longer for a slow connection. Here's a page describing the relevant properties: http://wiki.eclipse.org/Equinox/p2/TransportDebugging If there is more to this bug that I'm not getting then please provide more information about the network environment context, reproducibility, etc...as this timeout does not occur/is not reproducible in testing, or for other users.
I'm resolving this as worksforme, since a) I cannot duplicate this timeout in any environments that I/others have access to, and b) I believe the use of the system properties given in comment 2 will solve the issue WRT the environment for the original bug poster.
