[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [p2-dev] http instabilities

Thanks Scott, I'll report back to you with my findings! :)
HTH,
Ciao, hh 

-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Scott Lewis
Sent: Friday, August 28, 2009 6:01 PM
To: P2 developer discussions
Subject: Re: [p2-dev] http instabilities

Hi Helmut,

Haigermoser, Helmut wrote:
> Ciao Scott :)
> I was hoping you were gonna say that, so the new default is not the 
> UrlConnectionRetrieveFileTransfer.
> Hm, we did not explicitely specify any file transfer, so this might be

> about including a new plug-in in our product, or a property we need to

> set in config.ini/pluginCustomization.ini?
>   

Yes...if you want your product to include httpclient provider it needs
to be included in your feature/product...as it is in Eclipse.  Here are
the references to either an existing map file that you can use in your
build [1] if you choose to use a pre-built version of these plugins, or
a feature that has all of the relevant plugins [2]...if you would rather
build these plugins yourself.

> Well, we are trying to download artifacts, the one that failed was 
> only 2k so the size seems not to be terribly important (we have 
> giga-artifacts as well). Simple http downloads work whenever I try 
> them...
>   

Hmm.  Interesting...this may indicate a new/previously unidentified
problem with the URLConnection-based provider (or the JRE underneath
it).  Would you please open a bug to that effect against the
ecf.filetransfer component and include reproduce information (e.g. 
public server if possible)?  Just to be clear, I expect that if the
httpclient provider is included as described above that this issue
should go away for you, but I would like to get a bug opened for this
issue in any case (so that the JRE provider issue can be followed up
on/addressed).

Thanks...Again I suspect that the httpclient provider will not show
these issues, but please keep notified one way or another.

Scott


[1]
http://www.eclipse.org/external/rt/ecf/integration/v20090616-0832/ecf.fi
letransfer.map
-- this is a map file fragment for Eclipse 3.5.0 release [2] CVS:
dev.eclipse.org:/cvsroot/rt
org.eclipse.ecf/releng/features/org.eclipse.ecf.platform-feature

> Let me know what you need to better be able to help me, we have seen 
> issues with a publicly available amazon location as well so that you 
> could try yourselves...
>
> TIA,
> Ciao, hh
>
>
> -----Original Message-----
> From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] 
> On Behalf Of Scott Lewis
> Sent: Friday, August 28, 2009 5:19 PM
> To: P2 developer discussions
> Subject: Re: [p2-dev] http instabilities
>
> Hi Helmut,
>
> Could you describe a little more what is happening?  Is the server you

> are trying to reach slow or unreliable?  From the stack trace, you are

> apparently getting a read time out...which is typically caused because

> the server on the other end is not responding properly (or network 
> partition).  Is the server/file being accessed publicly available?  If

> so please make it known and we can/will give it a try.  Presumably 
> you've tried to access the resource via a web browser and everything 
> is fine with that.
>
> I see you are using the JRE provider...i.e. the 
> UrlConnectionRetrieveFileTransfer class in stack below.  Are you using

> this because you are behind an NTLMv2 network? (as opposed to the 
> httpclient provider, which is the default one for Eclipse 3.5).  Or 
> some other reason?
>
> Thanks,
>
> Scott
>
>
> Haigermoser, Helmut wrote:
>   
>> Ciao P2 :)
>> We recently had a surge of problems updating our products, using 
>> standard p2/ecf technologies, I'm hoping you've seen these and can 
>> point us at options to tweak the bevaviour to get by such issues...
>>
>> Here is the backtrace for our 3.5-based product:
>>
>> !ENTRY org.eclipse.equinox.p2.repository 4 1002 2009-08-28
>> 16:55:00.873 !MESSAGE Unable to read repository at http://<path to
>> artifact> !STACK 0
>> java.net.SocketTimeoutException: Read timed out
>> 	at java.net.SocketInputStream.socketRead0(Native Method)
>> 	at java.net.SocketInputStream.read(SocketInputStream.java:129)
>> 	at
>> java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>> 	at
>> java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
>> 	at
>> java.io.BufferedInputStream.read(BufferedInputStream.java:317)
>> 	at
>> sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)
>> 	at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
>> 	at
>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
>> n
>> ec
>> tion.java:1000)
>> 	at
>> org.eclipse.ecf.provider.filetransfer.retrieve.UrlConnectionRetrieveF
>> i
>> le
>>
Transfer.getDecompressedStream(UrlConnectionRetrieveFileTransfer.java:
>> 46
>> 2)
>> 	at
>> org.eclipse.ecf.provider.filetransfer.retrieve.UrlConnectionRetrieveF
>> i
>> le
>> Transfer.openStreams(UrlConnectionRetrieveFileTransfer.java:287)
>> 	at
>> org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTr
>> a
>> ns
>> fer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:808)
>> 	at
>> org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTr
>> a
>> ns
>> fer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:506)
>> 	at
>> org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveA
>> d
>> ap
>> ter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:98)
>> 	at
>> org.eclipse.equinox.internal.p2.repository.FileReader.sendRetrieveReq
>> u
>> es
>> t(FileReader.java:317)
>> 	at
>> org.eclipse.equinox.internal.p2.repository.FileReader.readInto(FileRe
>> a
>> de
>> r.java:263)
>> 	at
>> org.eclipse.equinox.internal.p2.repository.RepositoryTransport.downlo
>> a
>> d(
>> RepositoryTransport.java:70)
>> 	at
>> org.eclipse.equinox.internal.p2.repository.RepositoryTransport.downlo
>> a
>> d(
>> RepositoryTransport.java:121)
>> 	at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArti
>> f
>> ac
>> tRepository.downloadArtifact(SimpleArtifactRepository.java:472)
>> 	at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArti
>> f
>> ac
>> tRepository.downloadArtifact(SimpleArtifactRepository.java:455)
>> 	at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArti
>> f
>> ac
>> tRepository.getArtifact(SimpleArtifactRepository.java:522)
>> 	at
>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.get
>> A
>> rt
>> ifact(MirrorRequest.java:200)
>> 	at
>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.tra
>> n
>> sf
>> erSingle(MirrorRequest.java:175)
>> 	at
>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.tra
>> n
>> sf
>> er(MirrorRequest.java:159)
>> 	at
>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.per
>> f
>> or
>> m(MirrorRequest.java:95)
>> 	at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArti
>> f
>> ac
>> tRepository.getArtifact(SimpleArtifactRepository.java:511)
>> 	at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJo
>> b
>> .r
>> un(DownloadJob.java:64)
>> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>
>> TIA,
>> Ciao, hh
>> _______________________________________________
>> p2-dev mailing list
>> p2-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/p2-dev
>>   
>>     
>
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev
>   

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev