You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "LeoAugust19 (JIRA)" <ji...@apache.org> on 2018/08/02 03:35:00 UTC

[jira] [Created] (STORM-3171) java.lang.NoSuchMethodError in org.apache.storm:storm-kafka-monitor:jar:1.1.2 caused by dependency conflict issue

LeoAugust19  created STORM-3171:
-----------------------------------

             Summary: java.lang.NoSuchMethodError in org.apache.storm:storm-kafka-monitor:jar:1.1.2 caused by dependency conflict issue
                 Key: STORM-3171
                 URL: https://issues.apache.org/jira/browse/STORM-3171
             Project: Apache Storm
          Issue Type: Dependency upgrade
          Components: storm-kafka-monitor
    Affects Versions: 1.1.2
            Reporter: LeoAugust19 
             Fix For: 2.0.0


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 *<org.apache.zookeeper.server.quorum.flexible.QuorumMaj: void <init>(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.<init>(Ljava/util/Map;)V

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

         at org.apache.curator.framework.imps.CuratorFrameworkImpl.<init>(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

|  +- net.jpountz.lz4:lz4:jar:1.3.0:compile

|  +- org.xerial.snappy:snappy-java:jar:1.1.2.6:compile

|  \- org.slf4j:slf4j-api:jar:1.7.21:compile

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

|  \- org.apache.curator:curator-client:jar:4.0.0:compile

|     +- *org.apache.zookeeper:zookeeper:jar:3.4.6:compile (version managed from 3.5.3-beta)*

|     |  +- jline:jline:jar:0.9.94:compile

|     |  \- io.netty:netty:jar:3.9.9.Final:compile (version managed from 3.7.0.Final)

|     +- com.google.guava:guava:jar:16.0.1:compile (version managed from 20.0)

|     \- (org.slf4j:slf4j-api:jar:1.7.21:compile - version managed from 1.7.6; omitted for duplicate)

+- 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 a best solution, as 3.5.3-beta is not a release version.**

 

Thanks a lot!

Regards,

Leo



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)