cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pranav Saxena <pranav.sax...@citrix.com>
Subject RE: Master - jetty run failure
Date Wed, 03 Apr 2013 18:45:44 GMT
I happened to see that Hugo enabled the midonet plugin in both client/tomcatconf/componentContext.xml.in
  and  client/tomcatconf/nonossComponentContext.xml.in  on top of Dave's commit on supporting
midonet plugin.  Perhaps ,that fixed the issue actually.

-----Original Message-----
From: srivatsav.prasanna@gmail.com [mailto:srivatsav.prasanna@gmail.com] On Behalf Of prasanna
Sent: Thursday, April 04, 2013 12:10 AM
To: dev@cloudstack.apache.org
Subject: Re: Master - jetty run failure

I'm not seeing this on the latest master. Perhaps something wrong with nonOss component context?
Are you running nonOss by any chance?

On 3 April 2013 23:23, Pranav Saxena <pranav.saxena@citrix.com> wrote:
> Possible workaround  until that issue is fixed - Revering these two  commits - eddf7b9357bc18497b8cb16a6c6f3382ac52f61c
 and  44567453e0511e3090ac22518113b283cfa26b4b to have jetty running successfully.
>
> -----Original Message-----
> From: Likitha Shetty [mailto:likitha.shetty@citrix.com]
> Sent: Wednesday, April 03, 2013 11:15 PM
> To: dev@cloudstack.apache.org
> Cc: Hugo Trippaers
> Subject: Master - jetty run failure
>
> On latest master when I run jetty,
>
> ERROR [utils.component.ComponentContext] (Timer-2:) Unhandled 
> exception
> javax.naming.ConfigurationException: Could not find midonet API location in config
>         at com.cloud.network.element.MidoNetElement.configure(MidoNetElement.java:148)
>         at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
>         at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
>         at java.util.TimerThread.mainLoop(Timer.java:534)
>         at java.util.TimerThread.run(Timer.java:484)
> Exception in thread "Timer-2" java.lang.RuntimeException: Unable to configure com.cloud.network.element.MidoNetElement_EnhancerByCloudStack_c688f431
>         at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:114)
>         at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
>         at java.util.TimerThread.mainLoop(Timer.java:534)
>         at java.util.TimerThread.run(Timer.java:484)
> Caused by: javax.naming.ConfigurationException: Could not find midonet API location in
config
>         at com.cloud.network.element.MidoNetElement.configure(MidoNetElement.java:148)
>         at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
>         ... 3 more
>
> Thank you,
> Likitha
Mime
View raw message