Hi, we found a dependency conflict issue in org.apache.storm:storm-kafka-monitor:jar:1.1.2, caused by org.apache.zookeeper:zookeeper:jar. As shown in the following dependency tree, due to Maven version management, org.apache.zookeeper:zookeeper:jar:3.4.6 will be loaded, during the packaging process.

However, method (java.util.Map)> only defined in org.apache.zookeeper:zookeeper:jar 3.5.3-beta, so that there is a crash with the following stack trace when your project referencing the missing method.

Stack trace:

Exception in thread "main" java.lang.NoSuchMethodError: org.apache.zookeeper.server.quorum.flexible.QuorumMaj.(Ljava/util/Map;)V

         at org.apache.curator.framework.imps.EnsembleTracker.(EnsembleTracker.java:57)

         at org.apache.curator.framework.imps.CuratorFrameworkImpl.(CuratorFrameworkImpl.java:159)

         at org.apache.curator.framework.CuratorFrameworkFactory$Builder.build(CuratorFrameworkFactory.java:158)

         at org.apache.curator.framework.CuratorFrameworkFactory.newClient(CuratorFrameworkFactory.java:109)

Dependency tree:

org.apache.storm:storm-kafka-monitor:jar:1.1.2

+- org.apache.kafka:kafka-clients:jar:0.10.1.0:compile

+- org.apache.curator:curator-framework:jar:4.0.0:compile

+- com.googlecode.json-simple:json-simple:jar:1.1:compile

+- commons-cli:commons-cli:jar:1.3.1:compile

• junit:junit:jar:4.11:test

   - org.hamcrest:hamcrest-core:jar:1.3:test

Solution:

One choice is to upgrade org.apache.zookeeper:zookeeper:jar to 3.5.3-beta, but it is not the best solution, as 3.5.3-beta is not a release version.**

Thanks a lot!

Regards,

Leo