| Re: [ecf-dev] Random socket-timeout at org.eclipse.ecf.provider.filetransfer.retrieve.UrlConnectionRetrieveFileTransfer |
|
Hi Dileepa, Before discussing this error...I can reach this repository http://wso2.org/bamboo/artifact/WSO2CARBON-P2REPO/JOB1/build-97/P2-Repo/p2-repo/content.jar just fine using the httpclient 3.1-based provider (i.e. that's the one p2/Eclipse uses by default). I can see from the below that you are not using the httpclient-based provider (i.e. org.eclipse.ecf.provider.filetransfer.retrieve.UrlConnectionRetrieveFileTransfer is the UrlConnection-based provider). In general we've found the httpclient-based provider to be more reliable...and put more effort into making it more reliable...because that's what Eclipse/p2 are using. You can use the httpclient-based provider if you wish in your own application (you just need to include a few more plugins). Now, about the error you are seeing in the UrlConnection-based provider...I tried retrieving this url: http://wso2.org/bamboo/artifact/WSO2CARBON-P2REPO/JOB1/build-97/P2-Repo/p2-repo/artifacts.jar and it retrieved it without any exceptions in three ECF filetransfer test runs. So in other words, it seems I can't immediately reproduce the problem you are experiencing with this URL (I did artifacts.jar rather than content.jar because right now I'm on a slow link). It is quite possible, then, that what you are experiencing is due to some difference in system/configuration...it could be any one of: 1) Difference in java version (because it's using UrlConnection, the underlying socket handling code is different) 2) Difference in OS (maybe there's some lower-layer problem with Sockets on your system) 3) The java configuration (e.g. timeouts set very low)...i.e. the vm defines these as defaults for connect and read timeout sun.net.client.defaultConnectTimeout sun.net.client.defaultReadTimeout That's all I can think of for the moment. My initial suggestion is to add in/use the httpclient provider...with is in org.eclipse.ecf.provider.filetransfer.httpclient org.eclipse.ecf.provider.filetransfer.httpclient.ssl and the org.apache dependencies (o.a.commons.httpclient, o.a.commons.logging, and o.a.commons.codec) If that doesn't/can't work out, then I'm willing to help you figure out what's going wrong with the urlconnection-based provider...but the first thing to do there is to figure out why I can't reproduce what you are experiencing. Thanks, Scott On 5/17/2012 12:33 PM, Dileepa Jayakody wrote: Hi Guys, |