Bug 312400

Description d.zinato 2010-05-11 07:27:23 EDT

Build Identifier: 3.6.0.v20100422-1745

I have an application deployed with this structure:

configuration
  --> config.ini
plugins
  --> several plugins, RAP and BIRT included
org.eclipse.update.configurator_3.3.0.v20090312.jar
org.eclipse.osgi_3.6.0.v20100422-1745.jar
org.eclipse.equinox.common_3.6.0.v20100315.jar
my.starter.bundle

I developed it using org.eclipse.osgi_3.5.0.v20090520,org.eclipse.equinox.common_3.5.0.v20090520-1800,org.eclipse.update.configurator_3.3.0.v20090312.jar, as described in Equinox Quick Start (http://www.eclipse.org/equinox/documents/quickstart.php), and it always worked fine.


The flow at startime was this: at equinox start (i run this command: java -jar org.eclipse.osgi_3.5.0.v20090520.jar -console 5555), the framework installs and starts the common bundle, the update.configurator bundle and my starter bundle.
My starter bundle, at Activator.start, reads a file with the list of bundles to start; all these bundles have to be installed by update configurator.

With the new org.eclipse.osgi_3.6.0.v20100422-1745, the update configurator can't start using config.ini.
In the log, i found this error:

!SESSION 2010-05-11 12:35:40.906 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=it_IT
Command-line arguments:  -console 5555

!ENTRY org.eclipse.update.configurator 4 0 2010-05-11 12:35:41.796
!MESSAGE 
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.update.internal.configurator.ConfigurationActivator.start() of bundle org.eclipse.update.configurator.
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:806)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:370)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:374)
	at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1073)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:561)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:546)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:459)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:440)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)
Caused by: java.lang.Exception: Cannot initialize the Update Configurator
	at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize(ConfigurationActivator.java:107)
	at org.eclipse.update.internal.configurator.ConfigurationActivator.start(ConfigurationActivator.java:68)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
	... 11 more
Root exception:
java.lang.Exception: Cannot initialize the Update Configurator
	at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize(ConfigurationActivator.java:107)
	at org.eclipse.update.internal.configurator.ConfigurationActivator.start(ConfigurationActivator.java:68)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:370)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:374)
	at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1073)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:561)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:546)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:459)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:440)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)

!ENTRY org.eclipse.osgi 4 0 2010-05-11 12:35:42.171
!MESSAGE Bundle org.eclipse.update.configurator_3.3.0.v20090312 [2] is not active.

Now, THE STRANGE BEHAVIOUR is this: if i start equinox 3.6 from command line, and manually install the common and the update configurator bundles, i can start update configurator without any problem.
This is my config.ini file:

osgi.bundles=org.eclipse.equinox.common@2:start, org.eclipse.update.configurator@3:start, osgi.tkdata.bundle.impl.starter@5:start
eclipse.ignoreApp=true
osgi.clean=true

Reproducible: Always