Error during startup after updating features.

Submitted by preben on September 2, 2010 - 10:02

Error during startup after updating features. I updated greg. 3.5.0 with WSO2 Carbon - Carbon Common Patch Feature 3.0.1 WSO2 Carbon - Carbon UI Patch Feature - 3.0.1 WSO2 Carbon - Registry Extensions Patch Feature 3.0.1 from the p2 feature repository. After the update I get an exception during startup : The registry seems to work fine, but any exception (logged as INFO ???) bothers me. INFO - Initializing system... org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: javax.annotation.processing; version="0.0.0" at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272) at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:307) at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:108) at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:129) at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:143) at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330) Thanks Preben

Having same problems

Submitted by dvaughan.icfi.com on September 3, 2010 - 09:56.

Yep, any time I try to install extra Carbon features in ANY WSO2 product (tried WSAS, ESB, and Mashup Server), this is what happens. Completely breaks the server (cannot login to the admin console and, in Mashup Server, there is an error on all javascript services loading)... Is it not checking the dependencies correctly? Has installing new features worked for anyone?

Same here

Submitted by mark.activeingr... on September 4, 2010 - 23:36.

We are trying to get most of the WSO2 features available into a single install for ease of admin. I have spent a couple of days trying different combinations of initial install (Carbon base, ESB, WSAS etc) and then adding features. Each time, no matter where I start, I always get this error and on occasion I got it twice during restart, depending on which set of features The install I have running has most features added and has this error on startup. I have yet to find the affected artifact, if there is one, as all installed features tested seem unaffected. For those looking to combine several 'servers' into one i.e. ESB with IS, it is important to get the extra config files in place before adding the set of features to avoid extra errors. I started with an ESB install, then grabbed the identity.xml file in the 'repository/conf' folder of the IS download. I did the same for the other servers, grabbing the conf files for each. Then I started adding the features in. I still worry about the startup error as something must not be quite right.

Hi All, Can you guys please

Submitted by krishantha on September 9, 2010 - 20:58.

Hi All, Can you guys please send us the P2 repo URL that you have been using Thanks, Krishantha

p2 repo

Submitted by preben on September 9, 2010 - 22:09.

Hi Krishantha I have used http://dist.wso2.org/p2/carbon/releases/3.0.0/

Hi Preben, We were able to

Submitted by krishantha on September 10, 2010 - 00:55.

Hi Preben, We were able to reproduce this issue. Seems to be that jar needed to BPM is packed with other products. As a workaround can you remove org.apache.openjpa.openjpa-osgi-2.0.0.wso2v1.jar in pulugins directory and try out. (make sure to back up it) rm ../repository/components/plugins/org.apache.openjpa.openjpa-osgi-2.0.0.wso2v1.jar We verify the issue after removing the jar and it works. Thanks, Krishantha.

JIRA created :

Submitted by krishantha on September 10, 2010 - 00:58.

JIRA created : https://wso2.org/jira/browse/CARBON-7744 - Krishantha.

WSO2 Stratos Services

WSO2 Stratos

WSO2 Carbon Studio

Enterprise Service Bus

Business Rules Server

Governance Registry

Identity Server

Business Activity Monitor

Message Broker

Gadget Server

Business Process Server

Mashup Server

Data Services Server

Application Server

Complex Event Processing Server

Web Services Framework for PHP

Web Services Framework for C++

Web Services Framework for C

Carbon