cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rajesh Battala <>
Subject RE: Jetty Failing on latest master due to class UCS manager not Found
Date Thu, 28 Mar 2013 03:30:06 GMT
Jetty is failing to start on latest master building oss. 
Am on the latest master, building oss and starting jetty is failing with below error. 

Error creating bean with name 'globalLoadBalancingRulesServiceImpl':
Injection of autowired dependencies failed; nested exception is org.springframewor       
                                                  k.beans.factory.BeanCreationException: Could
not autowire field: protected org.apache.cloudstack.region.                              
                           gslb.GslbServiceProvider org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl._gslbProv
                                                         ider; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException:
No matching b                                                          ean of type [org.apache.cloudstack.region.gslb.GslbServiceProvider]
found for dependency: expected at le                                                     
    ast 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations:
{                                                          ject.Inject()}
        at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcess
        at org.springframe

> -----Original Message-----
> From: Murali Reddy []
> Sent: Thursday, March 28, 2013 8:24 AM
> To: Chip Childers; Kelven Yang
> Cc:;
> Subject: Re: Jetty Failing on latest master due to class UCS manager not Found
> On 28/03/13 7:42 AM, "Chip Childers" <> wrote:
> >On Wed, Mar 27, 2013 at 04:31:05PM -0700, Kelven Yang wrote:
> >> For UCS issue, I've put a fix in.
> >>
> >> For GSLB, a work around is to run non-OSS build, hopefully this can
> >>unlock  developers temporarily on master branch
> >
> >Good work-around for now.
> >
> >Murali - This appears to be something that we *all* missed realizing
> >prior to the merge of the GSLB functionality.  Can you sort this out
> >during your day today?
> I was running Non-oss builds, so could not hit this issue. My apologies for the
> breaking OSS build.
> Kelven,
> I am not sure how to fix this issue. If there is no implementing class, why should
> inject fail? I was under impression it will be set to null?
> I have this code in one of the managers in server, but the implementing class for
> GslbServiceProvider is only present in non-oss NetScaler plug-in. If you can
> suggest how to deal with this in Spring auto wiring that would be useful for me
> to quickly fix this.
> @Inject
>     protected GslbServiceProvider _gslbProvider;

View raw message