"Unable to acquire application service" error while launching Eclipse_问答_开发者

When ever I try to launch my eclipse I am getting the following exception an its not coming up.

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 org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
  at org.eclipse.equinox.launcher.Main开发者_如何转开发.basicRun(Main.java:514)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

Need help. Thanks.

The /configuration/config.ini file should contain org.eclipse.core.runtime@start in the commaseparated osgi.bundles property. Here is the default osgi.bundles property, maybe it was (accidently) changed during some upgrade:

osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start

You can if necessary override it by setting it as VM argument in /eclipse.ini:

-Dosgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start

I have had the same problem, and here's how I solved it: I added the plugin "org.eclipse.core.runtime" in the "plugins" section on the "configuration" tab of the .product editor. I set it's start level to default and auto-start to true. I removed other plugins. My reasoning was this: Eclipse is complaining that the org.eclipse.core.runtime isn't started, so let's make sure that it does start, and that it's the only plugin that's starting.

My application ran fine after I did this. I then inspected the config.ini to see what changed, and saw that org.eclipse.core.runtime was now changed to org.eclipse.core.runtime@start. This is consistent with BalusC's suggestion, I just did it from the .product editor.

Adding my two cents for those searching for "Ensure that the org.eclipse.core.runtime bundle is resolved and started":

Adding "arbitrary" bundles to the list of bundles just because it seems that they are missing is not always the best solution. Sometimes it can get quite frustrating, because those new plugins might depend on other missing bundles, which need even more bundles and so on...

So, before adding a new dependency to the list of required bundles, make sure you understand why the bundle is needed (the debugger is your friend!).

This question here doesn't provide enough information to make this a valid answer in all cases, but if you encounter the message that the org.eclipse.core.runtime is missing, try setting the eclipse.application.launchDefault system property to false, especially if you try to run an application which is not an "eclipse application" (but maybe just a headless runtime on top of equinox).

This link might come in handy: http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fruntime-options.html, look for the eclipse.application.launchDefault system property.

try running it from the Command Line as:

 >eclipse -clean

Or, you could run it using java instead of the default javaw, here:

 >eclipse -vm c:\jdks\java_1.5\jre\bin\java.exe

I got this problem with Mac OS Lion, after transfer OS/Data from an older machine to a new one.

Solved deleting the old eclipse folder (which I have in Applications folder) and copy eclipse folder again (same version, same unpacked zip file, no changes).

The accepted answer above is correct, except for it's not completely clear.

You need to add the following line to the bottom of the eclipse.ini file:

-Dosgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@

For me installing the jdk 1.8 solved the issue.

This error happen cause you deleted the config.ini file while you deleted the plugins. So, when it can not find configuration in config.ini when eclipse lauching， then it use default configuration which is not fit with your os. The following steps solve you problem:

Delete setting in configuration folder.
create a new config.ini file.
copy following setting and save:

osgi.splashPath = platform:/base/plugins/org.eclipse.platform  
osgi.bundles=org.eclipse.equinox.common@2:start, org.eclipse.update.configurator@3:start, org.eclipse.core.runtime@start  
eclipse.product=org.eclipse.sdk.ide  
osgi.instance.area.default=@user.home/workspace  
eof=eof

restart eclipse.

For me, what eventually did the trick was adding -clean at the start of eclipse.ini

In the Windows environment, running Eclipse as Administrator solved the issue. (Right click>Run as Administrator)

if you face this in 2021 or later better check that you have jdk 11 installed and is configured correctly. I downloaded the latest eclipse-jee-2021-06-R-win32-x86_64 and on running i got this issue. I checked the java version on my system and it was: 1.8 I downloaded the latest OpenJDK 11 configured it (JAVA_HOME in an environment variable and <JAVAHOME/bin entry in PATH environment varaible>) and the issue is gone.

I've been downloaded the "SDK ADT Bundle for Windows" adt-bundle-windows-x86.zip to "Documents and settings\myusername\My Documents\Downloads" and tried to unzip to a folder c:\Android

When all seems to be decompressed I saw some files where missing in the destination folder including the eclipse.ini.

I solved this by renaming adt-bundle-windows-x86.zip to a short name adt.zip, moving it to c:\ and repeating the decompression.

All is due to bad treatment of long file-names in windows

For those coming here having tried to run the application from a Windows command line, or batch file, and possibly those receiving the stated error message in a Rational Clear Case log file:

The PATH is very important to the processing of config files, and the following was required for me:

START "Clear Case" /D"C:\Program Files (x86)\Rational\ClearQuest\rcp\" "C:\Program Files (x86)\Rational\ClearQuest\rcp\clearquest.exe"

note the /D option.

Adding to a well-populated page:

I had this come up when I tried to move the eclipse installation to a different location on my drive. I tried grepping for the old directory path in the package, thinking perhaps I could fix it with sed, but the path was written in multiple formats and even found in binary files. I gave up, made a fresh install, and re-installed my plugins.

(Here's a question about moving an eclipse installation, but it didn't give me enough to make it work.)

I tried all the methods proposed here. I finally deleted the eclipse folder, extracted it again and now everything works perfectly.

I received this message trying to run STS 3.7.0 on java 6 jdk, after pointing to java jdk 7 (-vm param in STS.ini) the issue disappeared.

I got this problem somewhere on the logs and I saw that my java version was not 1.8 somehow. Upgrading it again to 1.8 solved my problem.

Download new eclipse or spring suite and open old workspace into new eclipse or STS

shawn: My eclipse have started when I extended bundles:

osgi.bundles=org.eclipse.equinox.common@2:start, org.eclipse.update.configurator@3:start, org.eclipse.core.runtime@start, org.eclipse.equinox.ds@start, org.eclipse.equinox.event@start

If none of the above answers works for you, try the following: Get the "org.eclipse.equinox.simpleconfigurator" and the "org.eclipse.update" folders found under the "eclipse\configuration" from a working Eclipse instance (can be the stock Eclipse downloaded from their website) and replace them in your Eclipse installation directory. This fixed it for me.

I tried all the answers above, but none of them worked for me, so I was forced to try something else. I just removed the whole package with settings org.eclipse.Java and it worked fine, starts again like before and even keeps all settings like color themes and others. Worked like charm.

On Linux or Mac go to /home/{your_user_name}/.var/app and run the following command:

 rm -r org.eclipse.Java

On Windows just find the same directory and move it to Trash.

After this is done, the settings and the errors are deleted, so Eclipse will start and re-create them with the proper settings.

When Eclipse starts it will ask for the workspace directory. When specified, everything works like before.

The only thing that worked for me was to run Eclipse using JAVA from the command line.

C:\Development_Tools\eclipse\java-2021-092\eclipse>java -jar plugins/org.eclipse.equinox.launcher_1.6.300.v20210813-1054.jar

This was executed from the folder where eclipse.exe resides.

I made my own shortcut for this and now use that shortcut instead of the one produced when installing Eclipse from their website.

in my opinion, if after trying all solution nothing wors then simply delete eclipse folder from your C://use/{pc}/eclipse and then again install the same eclipse . You will get all your data no need to worry.

This happens because of unexpected shutdown of your eclipse

delete processcenter.ini at location similar to: C:\IBM\IntegrationDesigner\v8.5\iid and then once IDE comes up, go to windows preference and put in the correct URL.