“Unable to acquire application service” error while launching Eclipse

匿名 (未验证) 提交于 2019-12-03 01:25:01

问题:

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.

回答1:

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 


回答2:

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.



回答3:

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.



回答4:

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).



回答5:

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:   1. Delete setting in configuration folder.   2. create a new config.ini file.   3. copy following setting and save:   4.  ` 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   `   5. restart eclipse. 


回答6:

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 


回答7:

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@ 


回答8:

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



回答9:

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.



回答10:

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.)



回答11:

shawn: My eclipse have started when I extended boundles:

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



回答12:

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



回答13:

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.



回答14:

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



回答15:

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.



回答16:

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.



标签
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!