cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohit Yadav <>
Subject Re: midonet-client and Guava dependency conflict
Date Fri, 10 Mar 2017 09:25:56 GMT
+1 Retire unsupported plugins, with at least comment them from the default build/packaging
in plugins/pom.xml?

Several plugins in 'plugins/network-elements/' may be removed from the default build/packaging.
However, 'midonet' was never fully implemented or completed and most definitely removed.


From: Simon Weller <>
Sent: 09 March 2017 21:37:08
Subject: Re: midonet-client and Guava dependency conflict

So this brings up a good discussion point. As Jeff points out, the Midonet plugin hasn't been
actively supported for almost 5 years. At what point do we consider retiring unsupported plugins?

- Si

From: Jeff Hair <>
Sent: Thursday, March 9, 2017 9:43 AM
Subject: Re: midonet-client and Guava dependency conflict

After doing some more digging, I have confirmed the following:

   - The midonet plugin is using the Maven Shade plugin to put a bunch of
   dependencies into itself.
   - The plugin hosted in this repository was last updated in 2013.
   - Most importantly: removing all the guava stuff out of the midonet
   plugin fixes this issue.

I have not had any success in applying to get Tomcat

GitHub - openwide-java/tomcat-classloader-ordered: A ...<> tomcat-classloader-ordered. A classloader for Apache Tomcat 8 which loads the jars
of WEB-INF lib in alphabetical order. Prior to version 8, Apache Tomcat ...

to load its jars in alphabetical order, for whatever reason. I tried
putting the Loader in various context definition locations, but it refuses
to work. Any ideas?

53 Chandos Place, Covent Garden, London  WC2N 4HSUK

On Thu, Mar 9, 2017 at 1:43 PM, Jeff Hair <> wrote:

> Hi,
> I'm deploying (not the vanilla version, but rather an upgraded
> version of our fork) on Tomcat 8. Management server startup fails with the
> following error:
> java.lang.IncompatibleClassChangeError: Found interface
>, but class was expected
> I've traced this down to the OutOfBandServiceManagerImpl. More
> specifically, when it tries to build the hostAlertCache using Guava's
> CacheBuilder. Deep in Guava, it's calling an "identity()" method on the
> Equivalence class.  All of the Guava classes are coming from guava-19.0
> except for com/google/common/base/Equivalence.class. The Equivalence
> class is being loaded from the midonet jar for some reason, and that
> version does not have the method needed. Thus, the error.
> This is because Tomcat apparently does not load jars in alphabetical order
> anymore, starting with version 8. An open ticket for them to fix this is
> here:
57129 – Regression. Load WEB-INF/lib jarfiles in ...<>
ASF Bugzilla – Bug 57129 Regression. Load WEB-INF/lib jarfiles in alphabetical order Last
modified: 2016-03-17 09:59:50 UTC

> It could be possible to "fix" this by using a custom ClassLoader to force
> Tomcat to load things alphabetically (testing that right now--and not
> really succeeding), but the proper fix is to have the midonet client not be
> packaging guava with itself. Does anyone know why this is?
> Jeff

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message