Application “…” could not be found in the registry.

Just spent a couple of hours debugging one of these and thought I would write it up in hopes that it makes things better.

My use case is that I’m calling my application from an API which means I’m dynamically starting it using the EclipseStarter class (with reflection since I can’t reference Eclipse stuff from the JAR file that my customers use).

Everything used to work in this particular set of tests (don’t they all say that?), and then when I run them I get the error below.

It turns out the problem was the plugin (bundle) that contained the application definition (in the plugin.xml) did not get resolved.  It did not get resolved because it depended on a plugin that did not exist.  However there is nothing in the logs that indicated there was a problem loading this plugin, it was just silently not loaded.  I only discovered this debugging the bundle resolution code and wondering why it was not resolved.

So if you get this error and you can’t think of any other reason for it, make sure all of your dependent bundles are present, and ;resoution=optional could be your friend.

This bug has been filed about this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=277058 (this happened in 3.4.2, so maybe it’s fixed in 3.5).

Caused by: java.lang.RuntimeException: Application “com.oaklandsw.transform.runtime.engine” could not be found in the registry. The applications available are: org.eclipse.equinox.app.error, org.eclipse.update.core.standaloneUpdate, org.eclipse.updat
e.core.siteOptimizer.
at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:242)
at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
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:386)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.oaklandsw.transform.runtime.RuntimeFactory.createRuntime(RuntimeFactory.java:229)
… 76 more

Advertisements

About francisu

VP, Architecture at Talend, overall responsible for product architecture and governance. Also maintainer of the Jenkins EC2 plugin.
This entry was posted in Uncategorized. Bookmark the permalink.

4 Responses to Application “…” could not be found in the registry.

  1. Benjamin Cabé says:

    I think you should probably try to add the “-debug” switch to your run method

  2. Kurt says:

    I’m encountering the same problem while attempting to use JFreeChart in a simple RCP (Eclipse 3.3.0). The RCP is the simple “RCP application with a view” template found in Eclipse. The JFreeChart jars are bundled into a seperate plugin per the example at http://www.vogella.de/articles/EclipseJFreeChart/article.html.

    I’ve found the simply adding the JFreeChart project as a dependency will cause the problem (Application not found in the registry). The log indicates that the JFreeChart bundle is missing… and I’m not sure what to do to get the app to find it (I’m new to RCP).

    Finally, I’ve found that I can avoid the problem and get the app to run with the JFreeChart example code simply by changing the ID of my RCP application. Does anyone know why this would seem to solve the problem?

    Thanks

  3. Kurt says:

    I believe that I have found the problem; the missing bundle (plugin) needed to be selected in the Launch Configuration… select project, right-click, , select Plug-ins tab, check the missing plugin.

    Kurt

  4. thens says:

    Yeah, this is usually (often for me) due to a wrong/corrupted “Run configuration”.
    Check all required plug-ins (“add required plugins”) and run the validation.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s