Hugo Trippaers
> Subject: RE: Master - jetty run failure
>
> Possible workaround until that issue is fixed - Revering these two commits -
> eddf7b9357bc18497b8cb16a6c6f3382ac52f61c and
> 44567453e0511e3090ac22518113b283cfa26b4b to have jetty running
> successfully.
>
ption that was being raised.
>
> >
> > -Original Message-
> > From: srivatsav.prasa...@gmail.com [mailto:srivatsav.prasa...@gmail.com]
> On Behalf Of prasanna
> > Sent: Thursday, April 04, 2013 12:10 AM
> > To: dev@cloudstack.apache.org
> > Su
pril 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
From: srivatsav.prasa...@gmail.com [mailto:srivatsav.prasa...@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 co
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
>
: 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
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.clo
