Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] read timeout problems
Odd that the information in the p2.index does not seem to be honoured. Maybe it continues if there is a problem delivering it (timeout), but I don't really know the logic around the p2.index file. This is Ian Bull's domain IIRC.

Regarding delivering an access denied status when a not found (404) should have been delivered is never good as you are basically saying "the file is there but you are not allowed to read it". 

One potential source of problems is if the update site has changed over time, and user once got hold of index information (in jars or xml files) that are no longer present - I can imagine checks being made in those cases for those specific files even if the p2.index file says otherwise. In this case delivering an access denied instead of 404 does not give the p2 client side a chance to correctly update the cached information as it will continue to believed the file is there. (I am just speculating though).

Hope that is of some help.
Regards

On Jan 6, 2012, at 15:21, Martin Lippert wrote:

Hi!

I am facing an interesting problem with update sites and I hope you can help me understand what is going on. We have plenty of composite update sites that all contain just an "compositeArtifact.xml" and a "compositeContent.xml" file. Those files work nicely.

But we are quite often getting reports from users that their installation stalls when they check for updates, complaining about "content.jar" could not be found (with a read timeout), same for "compositeArtifact.jar" or similar. Even if I put up a p2.index file like this:

version=1
metadata.repository.factory.order=compositeContent.xml,!
artifact.repository.factory.order=compositeArtifacts.xml,!

it doesn't change much, the "check for updates" is again complaining about a missing file "compositeArtifact.jar".

I don't know why and what to do about this.

One thing that is special here is the fact that our server (Amazon S3) is serving an XML document (containing an access denied error) when a resource is not found (like it is the case for those resources that p2 seems to try to download.

Any idea what I can do about this?

Thank you very much in advance for your help!!!

Cheers,
-Martin

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

Back to the top