[Odlparent-dev] Error while installing odl-restconf on master
|
Michael Vorburger <vorburger@...>
On Fri, Nov 17, 2017 at 7:31 AM, Faseela K <faseela.k@...> wrote:
Faseela, where do you see this, migrating what to Karaf 4? Is this a problem seen only in a downstream distribution we cannot see, which may have some wrong version dependency declaration somewhere, or something you are hitting using an upstream Karaf distribution -which one, the integration/distribution or the netvirt/vpnservice/distribution/karaf, or another one? Robert, Faseela pointed out to me that this ClassNotFoundException: org.eclipse.jetty.server.nio.SelectChannelConnector cannot be found by org.ops4j.pax.web.pax-web-jetty_4.3.0 shown below is exactly the same as what you discussed with Lori back in February on https://lists.opendaylight.org/pipermail/release/2017-February/009302.html ... Faseela also says there we still appear to have two different Jetty versions available / loaded (Faseela, could you reply to this with those additional details from IRC?). Is that intentional? IMHO something like that could be cause this kind of version mess confusion in OSGi, and lead to this kind of ClassNotFoundException... hoping Robert and/or Stephen know more about our Jetty version story which may help clarify what could be going on here.
|
|
|
|
Faseela K <faseela.k@...>
Hi Michael, We are not doing any new features downstream. We just have synced the master code, and built a distribution. The only feature we are trying to install is odl-restconf-all. This works in some of the setups, but not always.
When it works, I do see that HttpService is being pulled in by :
opendaylight-user@root>bundle:services | grep -B 9 HttpService OPS4J Pax Web - Jetty (392) provides: ------------------------------------- [org.ops4j.pax.web.service.spi.ServerControllerFactory]
OPS4J Pax Web - Runtime (394) provides: --------------------------------------- [org.ops4j.pax.web.service.spi.ServletListener] [org.ops4j.pax.web.service.spi.ServletListener] [org.osgi.service.cm.ManagedService] [org.osgi.service.http.HttpService, org.ops4j.pax.web.service.WebContainer]
SelectChannelConnector class is seen only in 8.1 version of jetty, I am not sure whether there is any ordering problem in this case. I do see two jetty-server related jars even in working as well as non-working setups.
org/eclipse/jetty/aggregate/jetty-all-server/8.1.14.v20131031/ org/eclipse/jetty/jetty-server/9.2.19.v20160908/
Thanks, Faseela
From: Michael Vorburger [mailto:vorburger@...]
On Fri, Nov 17, 2017 at 7:31 AM, Faseela K <faseela.k@...> wrote:
Faseela, where do you see this, migrating what to Karaf 4? Is this a problem seen only in a downstream distribution we cannot see, which may have some wrong version dependency declaration somewhere, or something you are hitting using an upstream Karaf distribution -which one, the integration/distribution or the netvirt/vpnservice/distribution/karaf, or another one?
Robert, Faseela pointed out to me that this ClassNotFoundException: org.eclipse.jetty.server.nio.SelectChannelConnector cannot be found by org.ops4j.pax.web.pax-web-jetty_4.3.0 shown below is exactly the same as what you discussed with Lori back in February on https://lists.opendaylight.org/pipermail/release/2017-February/009302.html ...
Faseela also says there we still appear to have two different Jetty versions available / loaded (Faseela, could you reply to this with those additional details from IRC?). Is that intentional? IMHO something like that could be cause this kind of version mess confusion in OSGi, and lead to this kind of ClassNotFoundException...
hoping Robert and/or Stephen know more about our Jetty version story which may help clarify what could be going on here.
M. -- Michael Vorburger, Red Hat
|
|
|
|
Faseela K <faseela.k@...>
Michael just now pointed out that downstream we are on an intermediate sync, where odlparent is on 2.0.4 and I see that upstream aaa uses odlparent 2.0.5 curently. We would like to first sync the latest master, and try this once again.
Thanks, Faseela
From: Faseela K
Hi Michael, We are not doing any new features downstream. We just have synced the master code, and built a distribution. The only feature we are trying to install is odl-restconf-all. This works in some of the setups, but not always.
When it works, I do see that HttpService is being pulled in by :
opendaylight-user@root>bundle:services | grep -B 9 HttpService OPS4J Pax Web - Jetty (392) provides: ------------------------------------- [org.ops4j.pax.web.service.spi.ServerControllerFactory]
OPS4J Pax Web - Runtime (394) provides: --------------------------------------- [org.ops4j.pax.web.service.spi.ServletListener] [org.ops4j.pax.web.service.spi.ServletListener] [org.osgi.service.cm.ManagedService] [org.osgi.service.http.HttpService, org.ops4j.pax.web.service.WebContainer]
SelectChannelConnector class is seen only in 8.1 version of jetty, I am not sure whether there is any ordering problem in this case. I do see two jetty-server related jars even in working as well as non-working setups.
org/eclipse/jetty/aggregate/jetty-all-server/8.1.14.v20131031/ org/eclipse/jetty/jetty-server/9.2.19.v20160908/
Thanks, Faseela
From: Michael Vorburger [mailto:vorburger@...]
On Fri, Nov 17, 2017 at 7:31 AM, Faseela K <faseela.k@...> wrote:
Faseela, where do you see this, migrating what to Karaf 4? Is this a problem seen only in a downstream distribution we cannot see, which may have some wrong version dependency declaration somewhere, or something you are hitting using an upstream Karaf distribution -which one, the integration/distribution or the netvirt/vpnservice/distribution/karaf, or another one?
Robert, Faseela pointed out to me that this ClassNotFoundException: org.eclipse.jetty.server.nio.SelectChannelConnector cannot be found by org.ops4j.pax.web.pax-web-jetty_4.3.0 shown below is exactly the same as what you discussed with Lori back in February on https://lists.opendaylight.org/pipermail/release/2017-February/009302.html ...
Faseela also says there we still appear to have two different Jetty versions available / loaded (Faseela, could you reply to this with those additional details from IRC?). Is that intentional? IMHO something like that could be cause this kind of version mess confusion in OSGi, and lead to this kind of ClassNotFoundException...
hoping Robert and/or Stephen know more about our Jetty version story which may help clarify what could be going on here.
M. -- Michael Vorburger, Red Hat
|
|
|
|
Ryan Goulding <ryandgoulding@...>
Let us know how it turns out!
toggle quoted messageShow quoted text
Thanks, Ryan
On Nov 17, 2017, at 7:51 AM, Michael Vorburger <vorburger@...> wrote:
|
|
|
|
Faseela K <faseela.k@...>
Hi,
The error below was coming due to a wrong jetty.xml configuration downstream, things are working once that is changed, even without a sync.
Thanks, Faseela
From: Ryan Goulding [mailto:ryandgoulding@...]
Let us know how it turns out!
Thanks,
|
|
|