I just went through Carbon dependencies. Removing MB features *might* *not*help to solve the issue here. Hector is used in many components.
For example, org.wso2.carbon.logging.service component. We need to come up with a solution for this. Anyway, I still would like to remove MB features from Cloud Controller. On Sun, Aug 11, 2013 at 10:54 PM, Isuru Perera <[email protected]>wrote: > Hi all, > > There is a problem upgrading the jclouds to latest version. > > When I start the Cloud Controller, the MB seems to be failing to start. > > Cartridge deployer is working fine when I tested on Amazon EC2! (which > means some jclouds APIs are working properly) > > Following are some details I found from OSGi console. > > *osgi> ls* > All Components: > ID State Component Name Located in bundle > *30 Unsatisfied > org.wso2.carbon.andes.internal.QpidServiceComponent > org.wso2.carbon.andes(bid=182)* > * > osgi> comp 30* > Component[ > name = org.wso2.carbon.andes.internal.QpidServiceComponent > factory = null > autoenable = true > immediate = true > implementation = org.wso2.carbon.andes.internal.QpidServiceComponent > state = Unsatisfied > properties = > {service.pid=org.wso2.carbon.andes.internal.QpidServiceComponent} > serviceFactory = false > serviceInterface = null > references = { > Reference[name = > org.wso2.carbon.andes.authentication.service.AuthenticationService, > interface = > org.wso2.carbon.andes.authentication.service.AuthenticationService, policy > = dynamic, cardinality = 1..1, target = null, bind = setAccessKey, unbind = > unsetAccessKey] > Reference[name = > org.wso2.andes.wso2.service.QpidNotificationService, interface = > org.wso2.andes.wso2.service.QpidNotificationService, policy = dynamic, > cardinality = 1..1, target = null, bind = setQpidNotificationService, > unbind = unsetQpidNotificationService] > Reference[name = server.configuration, interface = > org.wso2.carbon.base.api.ServerConfigurationService, policy = dynamic, > cardinality = 1..1, target = null, bind = setServerConfiguration, unbind = > unsetServerConfiguration] > Reference[name = event.broker, interface = > org.wso2.carbon.event.core.EventBundleNotificationService, policy = > dynamic, cardinality = 1..1, target = null, bind = > setEventBundleNotificationService, unbind = > unsetEventBundleNotificationService] > Reference[name = cassandra.service, interface = > org.wso2.carbon.cassandra.server.service.CassandraServerService, policy = > dynamic, cardinality = 1..1, target = null, bind = > setCassandraServerService, unbind = unsetCassandraServerService] > Reference[name = coordination.service, interface = > org.wso2.carbon.coordination.server.service.CoordinationServerService, > policy = dynamic, cardinality = 1..1, target = null, bind = > setCoordinationServerService, unbind = unsetCoordinationServerService] > } > located in bundle = org.wso2.carbon.andes_4.1.0 [182] > ] > Dynamic information : > The component is satisfied > All component references are satisfied > Component configurations : > Configuration properties: > service.pid = org.wso2.carbon.andes.internal.QpidServiceComponent > component.name = org.wso2.carbon.andes.internal.QpidServiceComponent > component.id = 29 > Instances: > *No instances were created because: Can not activate instance of > component org.wso2.carbon.andes.internal.QpidServiceComponent. The > activation throws: java.lang.NoClassDefFoundError: > me/prettyprint/hector/api/ConsistencyLevelPolicy* > > > Only problem I can think of is that I upgraded guava library to solve > following dependency when I create the Cloud Controller product. > > *jclouds Amazon EC2 provider 1.6.1.incubating (aws-ec2 1.6.1.incubating) > requires 'package com.google.common.base [14.0.0,15.0.0)'* > > Hector client also depends on guava. So, I'm guessing guava library update > might be causing issues. > > The hector component used in Cloud Controller just imports the > "com.google.common.base" package (without version). > > Hector is a client for Cassandra and it's coming from MB features. > > As I mentioned in another thread, I think we should remove MB features > from Cloud Controller. (As a quick solution to this issue) > > Please share your suggestions. > > Thanks! > > -- > Isuru Perera > about.me/chrishantha > -- Isuru Perera about.me/chrishantha
