Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Installation with p2 director fails and it's really slow
Installation with p2 director fails and it's really slow [message #1309257] Tue, 22 April 2014 11:29 Go to next message
Andras Kovi is currently offline Andras Kovi
Messages: 13
Registered: January 2014
Junior Member
I'm trying to create an automated installer in the command line. Currently I'm trying to install the Xtend SDK.

This is the script I'm running:
site_kepler="http://download.eclipse.org/releases/kepler"
site_xtext_releases="http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases"
eclipse/eclipse \
   -data $HOME/workspace-automated \
   -clean \
   -consolelog \
   -noSplash \
   -application org.eclipse.equinox.p2.director \
   -repository $site_kepler,$site_xtext_releases \
   -installIU org.eclipse.xtend.sdk.feature.group  \
   -profile SDKProfile \
   -followReferences \
   -bundlepool $HOME/.eclipse_bundlepool \
   -destination $PWD/eclipse 


But it fails:
!ENTRY org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2014-04-22 17:15:14.544
!MESSAGE Error while loading manipulator.
!STACK 0
java.lang.IllegalStateException: The framework persistent data location (/home/andras/installer/eclipse/configuration) is not the same as the framework configuration location (/home/andras/installer/eclipse/configuration).
	at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.checkConsistencyOfFwConfigLocAndFwPersistentDataLoc(EquinoxManipulatorImpl.java:65)
	at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.loadWithoutFwPersistentData(EquinoxManipulatorImpl.java:348)
	at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.load(EquinoxManipulatorImpl.java:319)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:55)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.SetProgramPropertyAction.execute(SetProgramPropertyAction.java:38)
	at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:38)
	at org.eclipse.equinox.internal.p2.engine.Phase.mainPerform(Phase.java:183)
	at org.eclipse.equinox.internal.p2.engine.Phase.perform(Phase.java:95)
	at org.eclipse.equinox.internal.p2.engine.PhaseSet.perform(PhaseSet.java:47)
	at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:75)
	at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44)
	at org.eclipse.equinox.internal.provisional.p2.director.PlanExecutionHelper.executePlan(PlanExecutionHelper.java:41)
	at org.eclipse.equinox.internal.provisional.p2.director.PlanExecutionHelper.executePlan(PlanExecutionHelper.java:23)
	at org.eclipse.equinox.internal.p2.director.app.DirectorApplication.executePlan(DirectorApplication.java:783)
	at org.eclipse.equinox.internal.p2.director.app.DirectorApplication.planAndExecute(DirectorApplication.java:776)
	at org.eclipse.equinox.internal.p2.director.app.DirectorApplication.performProvisioningActions(DirectorApplication.java:763)
	at org.eclipse.equinox.internal.p2.director.app.DirectorApplication.run(DirectorApplication.java:1063)
	at org.eclipse.equinox.internal.p2.director.app.DirectorApplication.start(DirectorApplication.java:1245)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Installation failed.
An error occurred while configuring the installed items
 session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null --> [R]org.eclipse.equinox.ds 1.4.101.v20130813-1853, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.SetProgramPropertyAction).
 Error while loading manipulator.
Caused by: Application failed, log file location: /home/andras/workspace-automated/.metadata/.log


I've seen a post that mentioned that the -destination and the -bundlepool arguments need to be absolute paths but using those hasn't helped. Also, the process is very slow. Much slower than in the GUI.

I'd highly appreciate someone helping me figure out a solution. Thank you.

[Updated on: Tue, 22 April 2014 11:30]

Report message to a moderator

Re: Installation with p2 director fails and it's really slow [message #1309563 is a reply to message #1309257] Tue, 22 April 2014 15:33 Go to previous messageGo to next message
Andras Kovi is currently offline Andras Kovi
Messages: 13
Registered: January 2014
Junior Member
I found it. And this is definitely a bug in the code.

if (fwPersistentDataLocation != null) {
	if (!fwConfigLocation.equals(fwPersistentDataLocation))
		throw new IllegalStateException(NLS.bind(Messages.exception_persistantLocationNotEqualConfigLocation, fwPersistentDataLocation.getAbsolutePath(), fwConfigLocation.getAbsolutePath()));


Now, the two values I see:

fwConfigLocation File (id=56) eclipse/configuration
fwPersistentDataLocation File (id=68) /home/andras/installer/eclipse/configuration

These are not the same files, but the absolute paths are the same. The message is misleading, and the check is inappropriate.

Though, I'm still not able to figure out a parametrization that works.
Re: Installation with p2 director fails and it's really slow [message #1310520 is a reply to message #1309563] Wed, 23 April 2014 04:26 Go to previous messageGo to next message
Mickael Istria is currently offline Mickael Istria
Messages: 745
Registered: July 2009
Location: Grenoble, France
Senior Member
On 04/22/2014 09:33 PM, Andras Kovi wrote:
> I found it. And this is definitely a bug in the code.

Feel free to report it
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Equinox and to
submit a patch using Gerrit
https://wiki.eclipse.org/Gerrit#Doing_Code_Reviews_with_Gerrit

HTH
--
Mickael Istria
My job: http://www.jboss.org/tools
My blog: http://mickaelistria.wordpress.com
My Tweets: http://twitter.com/mickaelistria
Re: Installation with p2 director fails and it's really slow [message #1310584 is a reply to message #1309257] Wed, 23 April 2014 05:14 Go to previous messageGo to next message
Andras Kovi is currently offline Andras Kovi
Messages: 13
Registered: January 2014
Junior Member
I got it working by decrypting the meaning of this title: Running inside the target application

What it really means: Installing into a running target application That is: the eclipse you are installing into must be running to use that command.

The other command never worked due to the exception and reasons mentioned in the precvious posts but when I started the installation while the eclipse was running, this version started to work.

Hope this clarification will help others.
Re: Installation with p2 director fails and it's really slow [message #1310839 is a reply to message #1310584] Wed, 23 April 2014 08:33 Go to previous messageGo to next message
Mickael Istria is currently offline Mickael Istria
Messages: 745
Registered: July 2009
Location: Grenoble, France
Senior Member
On 04/23/2014 11:14 AM, Andras Kovi wrote:
> The other command never worked due to the exception and reasons
> mentioned in the precvious posts but when I started the installation
> while the eclipse was running, this version started to work.
>
> Hope this clarification will help others.

Can you please share a link to a related bug report?
--
Mickael Istria
My job: http://www.jboss.org/tools
My blog: http://mickaelistria.wordpress.com
My Tweets: http://twitter.com/mickaelistria
Re: Installation with p2 director fails and it's really slow [message #1310991 is a reply to message #1310839] Wed, 23 April 2014 10:26 Go to previous message
Andras Kovi is currently offline Andras Kovi
Messages: 13
Registered: January 2014
Junior Member
I created the report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=433311
In retrospective is seems to explain the same issue as: https://bugs.eclipse.org/bugs/show_bug.cgi?id=329619 So may be closed as duplicate.
Previous Topic:[p2] mirror with transitive dependencies
Next Topic:API to cache a p2 repo description?
Goto Forum:
  


Current Time: Fri Aug 29 16:27:04 EDT 2014

Powered by FUDForum. Page generated in 0.01840 seconds