Eclipse Community Forums: Oomph » Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved a

Home » Eclipse Projects » Oomph » Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved a(Error during installed product launch)

Show: Today's Messages :: Show Polls :: Message Navigator

Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved a [message #1772133]

Tue, 05 September 2017 22:12

Ge Strait

Messages: 43
Registered: September 2017

Member

I've created my first Product setup in attempt to install an Eclipse product I've developed. After selecting my Product setup in Eclipse Installer and performing the product install, some things are "missing".
e.g.
No eclipse.ini is created by the installation.
No configuation/config.ini is created by the installation.

Can anyone suggest what I might be missing in my Product setup?

Currently my Product setup is very simple and only has a BrandingInfo and P2 Director that has requirement and a repository. The requirement is a feature that includes all features in my product. The repository is a p2 site that has all the features.

The Eclipse Installer shows:
...
Preparing to commit the provisioning operation.
Committing the provisioning operation.
Performing Eclipse Ini --launcher.appendVmargs
Skipping because C:\Users\IBM_ADMIN\OomphTest\product-tpftoolkit8\eclipse\eclipse.ini does not exist
Performing Eclipse Ini -Declipse.p2.max.threads=10
Performing Eclipse Ini -Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest
Performing Eclipse Ini -Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/
Performing Eclipse Ini -Xms1024M
...

The log in the configuration directory shows this launch error:

java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:78)

Report message to a moderator

Re: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolv [message #1772381 is a reply to message #1772133]

Fri, 08 September 2017 13:20

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

Do you have an actual product definition, i.e. a project with a *.product file? If not, there needs to be such a thing, or you can use (a copy of) the minimal product definition from the platform, e.g., like this for Oxygen into which your additional features are installed:


<?xml version="1.0" encoding="UTF-8"?>
<setup.p2:P2Task
    xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI"
    xmlns:setup.p2="http://www.eclipse.org/oomph/setup/p2/1.0"
    label="Eclipse Platform (Oxygen)">
  <requirement
      name="org.eclipse.platform.ide"
      versionRange="[4.7.0,4.8.0)"/>
  <requirement
      name="org.eclipse.platform.feature.group"
      versionRange="[4.7.0,4.8.0)"/>
  <requirement
      name="org.eclipse.rcp.feature.group"
      versionRange="[4.7.0,4.8.0)"/>
  <repository
      url="http://download.eclipse.org/releases/oxygen/201706281000"/>
</setup.p2:P2Task>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolv [message #1772394 is a reply to message #1772381]

Fri, 08 September 2017 14:22

Ge Strait

Messages: 43
Registered: September 2017

Member

Yes, my Releng has a Plug-in Development Project with a .product file. I've been thinking this is what is missing. Trying to figure out how to add it to the Product Setup. I'm guessing through the P2 Director Task?

Your Oxygen example indicates that the Oxygen repository has a Feature or Plug-in that has the .product file. Correct?

Currently my Project that has the .product file is not a Feature Project or Plug-in Project. So I've not been able to add it to my p2 repository. My p2 repository merely has all Features that the Content of the .product file specifies.

What I think I need to figure out is how to get my Project that has my .product file into my P2 repository. Which I assume means that Project needs to be a Feature or Plug-in project. Sound right?

Thanks.

Report message to a moderator

Re: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolv [message #1772397 is a reply to message #1772394]

Fri, 08 September 2017 14:43

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

No, it doesn't need to be a plug-in for feature product. Our installer product looks like this:

http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/products/org.eclipse.oomph.setup.installer.product

The IU for it does need to end up in your p2 repository. Some Maven/Tycho magic does that...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolv [message #1772513 is a reply to message #1772397]

Mon, 11 September 2017 18:46

Ge Strait

Messages: 43
Registered: September 2017

Member

Just a note to anyone who might read this thread, regarding how the issue was resolved.

1. Using info provide by Ed Merks, I understood that my p2 repository needed to have my product Installable Unit (IU). This IU contains the information in my product configuration file. i.e my .product file.

2. I went about trying to figure out how to get the project containing my product configuration file (.product file) into my product p2 repository. Thinking that I needed to do something "manual". Like maybe add my project of packaging type <packaging>eclipse-repository</packaging> that has my .product file, to my category.xml file, so the .product information would be in an IU in my p2 repository. As I've discovered, this is not the case.

3. What I did not understand is that there was already a product IU in my p2 repository. I believe the tycho-p2-repository-plugin plugin appears to be doing this.
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-repository-plugin</artifactId>
<version>${tycho-version}</version>
<configuration>
<includeAllDependencies>true</includeAllDependencies>
</configuration>
</plugin>

4. What I needed to do, was simply change my Product Setup file to point my P2 Director Task to the IU containing the information from my .product file.
Change the <requ irement> to point to the product IU created by Tycho...
To find my product IU I used the Repsitory Explorer:
a. Right-click on a repository under a P2 Directory task and select Explore.
b. Select the "Expert Mode" button in the Repository Explorer view
c. Look for the IU that ends in .product. e.g. my.cool.product
Set that IU as a P2 Director requirement in the Product Setup file
<setupTask
xsi:type="setup.p2:P2Task"
label="${scope.product.label} (${scope.product.version.label})">
<requirement
name="my.cool.product"
filter=""/>
<repository
url="http://my.server.com/p2repos/MyCoolProductP2"/>
</setupTask>
<description>My Product</description>
</version>

Thanks Ed!

Report message to a moderator

Re: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolv [message #1772529 is a reply to message #1772513]

Tue, 12 September 2017 02:25

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

I really appreciate that you provide the details that the next person with this problem needs in order to solve it. Thanks!

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolv [message #1861173 is a reply to message #1772133]

Tue, 26 September 2023 05:56

SANJEEV YADAV

Messages: 1
Registered: September 2023

Junior Member

I am facing same problem.

!SESSION 2023-09-26 10:31:38.366 -----------------------------------------------
eclipse.buildId=4.23.0.I20220308-0310
java.version=18.0.1
java.vendor=Eclipse Adoptium
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_IN
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product

This is a continuation of log file C:\Users\sanjeev\eclipse\jee-2022-03\eclipse\configuration\1695704498457.bak_3.log
Created Time: 2023-09-26 10:31:59.367

!ENTRY org.eclipse.osgi 4 0 2023-09-26 10:31:59.367
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:81)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:577)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
at org.eclipse.equinox.launcher.Main.run(Main.java:1467)

Report message to a moderator