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

Bug 352175

Summary: RCP Unable to acquire application service
Product: [Eclipse Project] Platform Reporter: Novi <novi.styarif>
Component: RuntimeAssignee: platform-runtime-inbox <platform-runtime-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: jp.satyam, mauromol, Olivier_Thomann
Version: 4.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Novi CLA 2011-07-14 23:23:06 EDT
Build Identifier: Hellios Version: 3.6.1

Hy Guys,

I'm develop RCP application, then i'm export this application use "Eclipse Product Export Wizard". I get file : configuration, jre, plugins and my application "MMQConsole.exe". But when i'm running the application i get some error, this error details :




!SESSION 2011-07-15 09:37:30.437 -----------------------------------------------
eclipse.buildId=M20100909-0800
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20090707 (JIT enabled)
J9VM - 20090706_38445_lHdSMr
JIT  - 20090623_1334_r8
GC   - 200906_09
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.osgi 2 0 2011-07-15 09:37:31.437
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-07-15 09:37:31.437
!MESSAGE Bundle org.eclipse.jdt.compiler.apt_1.0.300.v20100513-0845 [66] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.compiler.apt 2 0 2011-07-15 09:37:31.437
!MESSAGE Missing optionally imported package org.eclipse.jdt.internal.compiler.tool_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-07-15 09:37:31.437
!MESSAGE Bundle org.eclipse.jdt.compiler.tool_1.0.100.v_A68_R36x [67] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.compiler.tool 2 0 2011-07-15 09:37:31.437
!MESSAGE Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-1.6

!ENTRY org.eclipse.osgi 4 0 2011-07-15 09:37:31.437
!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:74)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:618)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1407)


Perhaps, anyone can help this problem. I don't know how to fix this problem.


Best Regard,

Novi Styarif Wicaksono

Reproducible: Always
Comment 1 Olivier Thomann CLA 2011-07-15 09:42:32 EDT
Moving to Platform/Runtime
Comment 2 Mauro Molinari CLA 2012-11-12 05:18:34 EST
I'm experiencing this problem sometimes when trying to start Eclipse 4.2.1 (working on M20121107-1200).

While on the splash screen, application terminates and writes a log file in <eclipse_home>/configuration containing the following:

!SESSION 2012-11-12 11:12:18.173 -----------------------------------------------
eclipse.buildId=M20121107-1200
java.version=1.7.0_01
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=it_IT
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -debug -consoleLog

!ENTRY org.eclipse.osgi 2 0 2012-11-12 11:12:25.366
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-12 11:12:25.367
!MESSAGE Bundle org.codehaus.groovy_1.7.10.xx-20121024-2100-e42 [941] was not resolved.
!SUBENTRY 2 org.codehaus.groovy 2 0 2012-11-12 11:12:25.367
!MESSAGE The bundle is disabled: "org.eclipse.pde.ui:Disabled via PDE"
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-12 11:12:25.368
!MESSAGE Bundle org.codehaus.groovy_1.8.6.xx-20121024-2100-e42 [942] was not resolved.
!SUBENTRY 2 org.codehaus.groovy 2 0 2012-11-12 11:12:25.370
!MESSAGE The bundle is disabled: "org.eclipse.pde.ui:Disabled via PDE"

!ENTRY org.eclipse.osgi 2 0 2012-11-12 11:12:26.598
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-12 11:12:26.599
!MESSAGE Bundle org.codehaus.groovy_1.7.10.xx-20121024-2100-e42 [941] was not resolved.
!SUBENTRY 2 org.codehaus.groovy 2 0 2012-11-12 11:12:26.599
!MESSAGE The bundle is disabled: "org.eclipse.pde.ui:Disabled via PDE"
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-12 11:12:26.600
!MESSAGE Bundle org.codehaus.groovy_1.8.6.xx-20121024-2100-e42 [942] was not resolved.
!SUBENTRY 2 org.codehaus.groovy 2 0 2012-11-12 11:12:26.601
!MESSAGE The bundle is disabled: "org.eclipse.pde.ui:Disabled via PDE"

!ENTRY org.eclipse.osgi 4 0 2012-11-12 11:12:26.612
!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:74)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

!ENTRY org.eclipse.osgi 2 0 2012-11-12 11:12:26.952
!MESSAGE Info: cycle(s) found while stopping bundles: [[org.springframework.web,org.springframework.orm,org.springframework.context,org.springframework.transaction,org.springframework.oxm,org.springframework.jdbc],[org.springframework.ide.eclipse.metadata,org.springframework.ide.eclipse.beans.core.metadata,org.springframework.ide.eclipse.beans.ui]].

I have to retry the operation (clicking again on the Eclipse icon) in order to make it start.

It happens about once out of ten times.
Comment 3 Mauro Molinari CLA 2012-11-12 05:19:35 EST
I forgot to say it happens after I choose the workspace to open Eclipse on.
Comment 4 Mauro Molinari CLA 2013-01-11 05:46:59 EST
This is happening quite frequently. Is there a way (debug option or such) to try to gather more information to understand what's going on?
Comment 5 Paul Webster CLA 2013-01-11 09:15:20 EST
You can get the .options file from the org.eclipse.osgi bundle (rename it to something like debug.options), turn on OSGi/framework debugging, and then use -debug debug.options to activate debugging.

Be sure to re-direct your stdout/stderr to a log file.

PW
Comment 6 jayaprakash CLA 2013-07-25 04:27:20 EDT
I am also getting the same exception, but only with jre 1.7.0_25. My application works fine with other jres. My application's target platform is eclipse 3.5. See the stack trace here:
================================================================
!ENTRY org.eclipse.osgi 4 0 2013-07-25 08:10:22.227
!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:74)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at com.apc.config.isxdesigner.launcher.Main.invokeFramework(Main.java:460)
	at com.apc.config.isxdesigner.launcher.WebStartMain.basicRun(WebStartMain.java:354)
	at com.apc.config.isxdesigner.launcher.Main.run(Main.java:1113)
	at com.apc.config.isxdesigner.launcher.WebStartMain.main(WebStartMain.java:132)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at com.sun.javaws.Launcher.executeApplication(Unknown Source)
	at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
	at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
	at com.sun.javaws.Launcher.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
====================================================================
I searched a lot find solution for this. Many people suggested me to change the order of plugin load. After changing in load order, I could see different error, but application didn't launch. 
Order of loading plugins is here :org.eclipse.core.runtime@2:start,org.eclipse.equinox.ds@3:start,org.eclipse.core.contenttype@2:start,org.eclipse.equinox.common@3:start,org.apache.xerces@3:start,org.eclipse.equinox.registry@3:start,javax.xml@3:start,org.h2@3:start,org.hibernate@3:start

Please help me resolve this.
Thanks in advance
Comment 7 Paul Webster CLA 2013-07-25 14:54:57 EDT
(In reply to comment #6)
> I am also getting the same exception, but only with jre 1.7.0_25. My
> application works fine with other jres. My application's target platform is
> eclipse 3.5. See the stack trace here:


There's no fix, and we're waiting on more debugging information.  See comment #5

PW
Comment 8 Lars Vogel CLA 2019-11-27 07:46:35 EST
This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.