Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Could not acquire the framework manipulator service
Could not acquire the framework manipulator service [message #1420418] Wed, 10 September 2014 00:52 Go to next message
Timm Baumeister is currently offline Timm BaumeisterFriend
Messages: 14
Registered: July 2012
Junior Member
I am trying to migrate an eclipse 3.8 rcp application to 4.4. Unfortunately I can't get the auto update to work. This is the exception that gets thrown during the execution of the provisioning job:


INFO  : An error occurred while unconfiguring the items to uninstall
INFO  : session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Unconfigure, operand=[R]ecabia_main.product.executable.win32.win32.x86.Ecabia 1.1.338 --> null, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.SetLauncherNameAction).
ERROR : Could not acquire the framework manipulator service.
java.lang.IllegalStateException: Could not acquire the framework manipulator service.
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:45) ~[org.eclipse.equinox.p2.touchpoint.eclipse_2.1.200.v20140512-1650.jar:na]
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getLauncherData(LazyManipulator.java:118) ~[org.eclipse.equinox.p2.touchpoint.eclipse_2.1.200.v20140512-1650.jar:na]
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.SetLauncherNameAction.setLauncher(SetLauncherNameAction.java:44) ~[org.eclipse.equinox.p2.touchpoint.eclipse_2.1.200.v20140512-1650.jar:na]
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.SetLauncherNameAction.execute(SetLauncherNameAction.java:30) ~[org.eclipse.equinox.p2.touchpoint.eclipse_2.1.200.v20140512-1650.jar:na]
	at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:38) ~[org.eclipse.equinox.p2.engine_2.3.0.v20140506-1720.jar:na]
	at org.eclipse.equinox.internal.p2.engine.Phase.mainPerform(Phase.java:183) ~[org.eclipse.equinox.p2.engine_2.3.0.v20140506-1720.jar:na]
	at org.eclipse.equinox.internal.p2.engine.Phase.perform(Phase.java:95) ~[org.eclipse.equinox.p2.engine_2.3.0.v20140506-1720.jar:na]
	at org.eclipse.equinox.internal.p2.engine.PhaseSet.perform(PhaseSet.java:47) ~[org.eclipse.equinox.p2.engine_2.3.0.v20140506-1720.jar:na]
	at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:75) ~[org.eclipse.equinox.p2.engine_2.3.0.v20140506-1720.jar:na]
	at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44) ~[org.eclipse.equinox.p2.engine_2.3.0.v20140506-1720.jar:na]
	at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:174) ~[org.eclipse.equinox.p2.operations_2.4.0.v20131119-0908.jar:na]
	at org.eclipse.equinox.p2.operations.ProfileModificationJob.runModal(ProfileModificationJob.java:79) ~[org.eclipse.equinox.p2.operations_2.4.0.v20131119-0908.jar:na]
	at org.ecabia.das.p2.P2Util.checkForUpdates(P2Util.java:232) [org.ecabia.das_1.1.338.jar:na]
	at org.ecabia.das.p2.P2Util.doCheckForUpdates(P2Util.java:130) [org.ecabia.das_1.1.338.jar:na]
	at org.ecabia.das.p2.P2Util.access$0(P2Util.java:89) [org.ecabia.das_1.1.338.jar:na]
	at org.ecabia.das.p2.P2Util$1$1.run(P2Util.java:73) ~[org.ecabia.das_1.1.338.jar:na]
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) ~[org.eclipse.jface_3.10.0.v20140604-0740.jar:na]



I read that the org.eclipse.osgi.compatibility.state fragment needs to be added for compatibility which I already have.

I am out of ideas. Any help would be greatly appreciated.

[Updated on: Wed, 10 September 2014 01:07]

Report message to a moderator

Re: Could not acquire the framework manipulator service [message #1420863 is a reply to message #1420418] Wed, 10 September 2014 15:41 Go to previous messageGo to next message
Timm Baumeister is currently offline Timm BaumeisterFriend
Messages: 14
Registered: July 2012
Junior Member
Fixed it by adjusting start levels:

index.php/fa/19101/0/
Re: Could not acquire the framework manipulator service [message #1625799 is a reply to message #1420418] Fri, 20 February 2015 16:53 Go to previous message
Flavio Donze is currently offline Flavio DonzeFriend
Messages: 204
Registered: July 2009
Location: Switzerland
Senior Member
I had to add "org.eclipse.osgi.compatibility.state" to my feature and the following lines to my product:
   <configurations>
      <plugin id="org.eclipse.core.runtime" autoStart="true" startLevel="0" />
      <plugin id="org.eclipse.equinox.common" autoStart="true" startLevel="2" />
      <plugin id="org.eclipse.equinox.ds" autoStart="true" startLevel="2" />
      <plugin id="org.eclipse.equinox.event" autoStart="true" startLevel="2" />
      <plugin id="org.eclipse.equinox.simpleconfigurator" autoStart="true" startLevel="1" />
      <plugin id="org.eclipse.osgi" autoStart="true" startLevel="-1" />
   </configurations>


Prozessmanagement und Qualit├Ątsmanagement Software QMS/IMS
https://www.scodi.ch
Previous Topic:loading classes by classloader at run time
Next Topic:BundleFileWrapper does not wraps the invocation to getResourceURL
Goto Forum:
  


Current Time: Sat Sep 22 18:58:06 GMT 2018

Powered by FUDForum. Page generated in 0.01513 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top