[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Problem for update a big bundle

Hi Pierre-Yves,

I'm really surprised that killing the process would result in problems especially like the first one. This would mean that somehow the system was not able to create the artifact repository manager.... which is the only thing that is being accessed there.
This is definitely an interesting problem!
Could you please open bug reports capturing the two problems and we'll look into it (https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Equinox).

Also could you please try the following and report: once you killed the process, and before restarting the system, delete the content of the org.eclipse.osgi folder contained in the configuration folder.



I’ve a problem for update a product with a big bundle (~350 Mo).
I try to test recovery mode for P2. For this, I use an unit test to update a product with a big bundle and I kill the process during the download. After, I retry to update after. But I’ve an NullPointerException thrown by org.eclipse.equinox.internal.p2.touchpoint.eclipse.Util.getBundlePoolRepository (line 79).
After several test, I find 2 problems.
First : the problem explain above
Second : when I want to update my product (version n) with a big bundle (version n+1), I’ve an NullPointerException thrown by org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getMaximumThreads (line 737).
If I change the big bundle with a very small bundle (~2Ko), I don’t have problem to update.
If I retry with the big bundle, the problem is back.
For information : Dev platform is on Seven 64Bit
I’ve you an idea on this problem ?
Pierre-Yves Folens
p2-dev mailing list