Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 261840

Summary: IllegalStateException: 'The profile is currently in use' while updating my install
Product: [Eclipse Project] Equinox Reporter: Frederic Fusier <frederic_fusier>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: simon_kaegi
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard:

Description Frederic Fusier CLA 2009-01-21 10:08:27 EST 
I have made a fresh install with build I20090113-0918 and I wanted to update it with last I-build but I systematically got the following exception:

java.lang.IllegalStateException: The profile is currently in use.
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry.lockProfile(SimpleProfileRegistry.java:655)
at org.eclipse.equinox.internal.provisional.p2.engine.Engine.perform(Engine.java:51)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningUtil.performProvisioningPlan(ProvisioningUtil.java:274)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProfileModificationOperation.doExecute(ProfileModificationOperation.java:59)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningOperation.execute(ProvisioningOperation.java:37)
at org.eclipse.equinox.internal.provisional.p2.ui.ProvisioningOperationRunner$1.run(ProvisioningOperationRunner.java:80)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Set severity to major because I cannot longer update I-builds on this machine. 

In fact this exception occurred while trying to update previous build from on old fresh install, but I was in a hurry and I decided to apply a simple workaround: i.e. make a fresh install of build I20090113-0918... Then, I was definitely convinced that the problem would vanish on next update...
Comment 1 Simon Kaegi CLA 2009-01-21 10:23:31 EST 
There is a recently introduced (and now fixed) timing situation in the engine where the work we do to determine the size of the required downloads interferes with the regular update.

A possible but not especially good workaround is to wait until you see the size of things you're going to install/update before hitting next/finish to give a chance for the sizing operation to complete.

*** This bug has been marked as a duplicate of bug 261573 ***
Comment 2 Frederic Fusier CLA 2009-01-21 10:32:19 EST 
(In reply to comment #1)
> There is a recently introduced (and now fixed) timing situation in the engine
> where the work we do to determine the size of the required downloads interferes
> with the regular update.
> 
> A possible but not especially good workaround is to wait until you see the size
> of things you're going to install/update before hitting next/finish to give a
> chance for the sizing operation to complete.
> 
> *** This bug has been marked as a duplicate of bug 261573 ***
> 
The workaround works :-)
Thanks