Resolution:
Description:
===========

TIBCO BusinessEvents Studio fails to start successfully, it throws an error and it creates an error log file.

Environment:
===========

  o BusinessEvent 4.x
  o All Operating Systems

Symptoms:
=========
When launching TIBCO BusinessEvents Studio, it throws an error and creates an error log file.  This issue has been seen after upgrading the existing TIBCO BusinessEvents ver 4.0 to  TIBCO BusinessEvents ver 4.0.1.

Sample entries in logfile:
===================

!ENTRY org.eclipse.osgi 4 0 2010-11-15 13:49:23.031
!MESSAGE An error occurred while automatically activating bundle org.eclipse.update.configurator (124).
!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:1028)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:265)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)


Cause:
======

This is due to an issue in the Eclipse environment where it maintains certain metadata information to improve performance and startup times. This typically occurs if a new plugin with the same version is installed over an existing one.  In this case, Eclipse thinks that it already has the plugin’s manifest cached, so it doesn’t look at the new manifest file.  If the new plugin has a new dependency for instance, then this dependency will not be seen and you might get the error.


Resolution:
========

Run the following command from the shell/command prompt.

&ltBE4-home>\studio\eclipse\studio -clean

-clean is an eclipse option to clean out certain metadata that is kept in the eclipse configuration/workspace area.  To improve performance and startup time, eclipse caches some information, such as plugin manifest information (versions, dependencies, etc), rather than extracting/parsing them every time.  When –clean is done, this information is wiped out and the cache is recreated.

References
=========

This is mentioned in our TIBCO BusinessEvents Installation guide - Chapter 3 - under Post Installation Tasks for All Platforms.


Note:
====

Running –clean –initialize will not actually start Studio (because of the –initialize part).  It will clean out the metadata without starting the application.  There is no need for the –initialize in this case, -clean will suffice, and will start the application.