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

Bug 270794

Summary: "No application id has been found" while launching self-hosted Eclipse
Product: [Eclipse Project] Equinox Reporter: Pawel Pogorzelski <pawel.pogorzelski1>
Component: FrameworkAssignee: equinox.framework-inbox <equinox.framework-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: caniszczyk, tjwatson
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Log
none
Screen none

Description Pawel Pogorzelski CLA 2009-04-01 10:20:20 EDT
Created attachment 130563 [details]
Log

Build ID: I20090331-0901

After switching to I20090331-0901 I got this error while launching a self-hosted Eclipse. This error doesn't happen right after the update, so I don't have a repeatable steps so far. But it happened tree times today.

The full log in the attachment.

java.lang.RuntimeException: No application id has been found.
	at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:236)
	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:368)
	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:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:324)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:556)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1284)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1260)
Comment 1 Thomas Watson CLA 2009-04-01 13:37:38 EDT
This seems to indicate that the -product or -application argument was not used to launch the self-hosted instance.  Chris, did something in PDE change that could cause this to happen?
Comment 2 Chris Aniszczyk CLA 2009-04-01 14:46:58 EDT
The only changes that went in recently around this was the support of launching a product with only an application, not a -product

Here's the logic:

// If a product is specified, then add it to the program args
		if (configuration.getAttribute(IPDELauncherConstants.USE_PRODUCT, false)) {
			String product = configuration.getAttribute(IPDELauncherConstants.PRODUCT, ""); //$NON-NLS-1$
			if (product.length() > 0) {
				programArgs.add("-product"); //$NON-NLS-1$
				programArgs.add(product);
			} else { // TODO product w/o an application and product... how to handle gracefully?
				programArgs.add("-application"); //$NON-NLS-1$
				programArgs.add(configuration.getAttribute(IPDELauncherConstants.APPLICATION, "")); //$NON-NLS-1$
			}
		} else {
			// specify the application to launch
			programArgs.add("-application"); //$NON-NLS-1$
			programArgs.add(configuration.getAttribute(IPDELauncherConstants.APPLICATION, TargetPlatform.getDefaultApplication()));
		}


My guess is that you're launching w/o an application or a product that doesn't have a product OR application.
Comment 3 Pawel Pogorzelski CLA 2009-04-02 04:12:59 EDT
Created attachment 130656 [details]
Screen

(In reply to comment #2)
> <text deleted/>
> My guess is that you're launching w/o an application or a product that doesn't
> have a product OR application.
> 

Let me clear it a bit. I switched to the I20090331-0901 build and was able to work with self-hosted Eclipse for a while. Then, without any change in Debug Configuration, it stopped working. Moreover I don't have any clue on how to get it back working.

The attachment shows my configuration in this area, it's a standard one.
Comment 4 Pawel Pogorzelski CLA 2009-04-02 08:44:03 EDT
Got the steps, narrowed as much as possible:

1. I have a fresh I20090331-0901 installation with a clean workspace
2. It's launched using java 1.6.0_10-rc from Sun
3. It's possible to launch a self-hosted Eclipse
4. I change the Java Runtime Environment under Debug Configurations and specify java 1.4.2_18-b06 from Sun
5. When I start self-hosted Eclipse I got the error from comment 0

Hope it helps.
Comment 5 Thomas Watson CLA 2009-04-02 09:33:33 EDT
(In reply to comment #4)
> Got the steps, narrowed as much as possible:
> 
> 1. I have a fresh I20090331-0901 installation with a clean workspace
> 2. It's launched using java 1.6.0_10-rc from Sun
> 3. It's possible to launch a self-hosted Eclipse
> 4. I change the Java Runtime Environment under Debug Configurations and specify
> java 1.4.2_18-b06 from Sun
> 5. When I start self-hosted Eclipse I got the error from comment 0
> 
> Hope it helps.
> 

Ah, that is because of bug 270535.  Should be fixed in the respin of the I-Build this week.

*** This bug has been marked as a duplicate of bug 270535 ***