cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Hair <>
Subject midonet-client and Guava dependency conflict
Date Thu, 09 Mar 2017 13:43:20 GMT

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

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?


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