java.lang.NoSuchFieldError: addr
- [x] I have searched the issues of this repository and believe that this is not a duplicate.
Environment
- Dubbo version: 3.2.0-beta.4
- Operating System version: mac 13.1
- Java version: jdk17
Steps to reproduce this issue
java.lang.NoSuchFieldError: addr at org.apache.curator.framework.imps.EnsembleTracker.configToConnectionString(EnsembleTracker.java:185) ~[curator-framework-4.3.0.jar:4.3.0] at org.apache.curator.framework.imps.EnsembleTracker.processConfigData(EnsembleTracker.java:206) ~[curator-framework-4.3.0.jar:4.3.0] at org.apache.curator.framework.imps.EnsembleTracker.access$300(EnsembleTracker.java:50) ~[curator-framework-4.3.0.jar:4.3.0] at org.apache.curator.framework.imps.EnsembleTracker$2.processResult(EnsembleTracker.java:150) ~[curator-framework-4.3.0.jar:4.3.0] at org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:883) ~[curator-framework-4.3.0.jar:4.3.0] at org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:653) ~[curator-framework-4.3.0.jar:4.3.0] at org.apache.curator.framework.imps.WatcherRemovalFacade.processBackgroundOperation(WatcherRemovalFacade.java:152) ~[curator-framework-4.3.0.jar:4.3.0] at org.apache.curator.framework.imps.GetConfigBuilderImpl$2.processResult(GetConfigBuilderImpl.java:222) ~[curator-framework-4.3.0.jar:4.3.0] at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:636) ~[zookeeper-3.7.0.jar:3.7.0] at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:555) ~[zookeeper-3.7.0.jar:3.7.0] Pls. provide [GitHub address] to reproduce this issue.
MultipleAddresses does not contain getAddress()
Expected Behavior
Actual Behavior
If there is an exception, please attach the exception trace:
Just put your stack trace here!
检查下 curator 的版本,这个一般都是 zookeeper 的版本有冲突导致的
我临时升级了版本,暂时解决了问题, 但是这个版本号是 3.2.0-beta.4 应该在 3.2.0-beta.4 上同步升级才对
<dependency>
<groupId>org.apache.zookeeper</groupId>
<artifactId>zookeeper</artifactId>
<version>3.8.0</version>
</dependency>
<dependency>
<groupId>org.apache.curator</groupId>
<artifactId>curator-framework</artifactId>
<version>5.4.0</version>
</dependency>
<dependency>
<groupId>org.apache.curator</groupId>
<artifactId>curator-recipes</artifactId>
<version>5.4.0</version>
</dependency>
<dependency>
<groupId>org.apache.curator</groupId>
<artifactId>curator-x-discovery</artifactId>
<version>5.4.0</version>
</dependency>
应该在 3.2.0-beta.4 上同步升级才对
Dubbo 不会传递 zookeeper / curator 的依赖,这个是用户自己选择的。目前 curator 4.x / 5.x 和 zookeeper > 3.4.x 都是全系列支持的。
应该在 3.2.0-beta.4 上同步升级才对
Dubbo 不会传递 zookeeper / curator 的依赖,这个是用户自己选择的。目前 curator 4.x / 5.x 和 zookeeper > 3.4.x 都是全系列支持的。
是我描述的有问题,是该项目所依赖的curator是4.3.0版本:dubbo-dependencies-zookeeper-curator5 3.2.0-beta.4
curator 4.3.0 应该是可以用的,主要是 zookeeper 的版本
我找到了变更记录,从5.1.0 降级到4.3.0了,同时dubbo-dependencies-zookeeper-curator 也从4.2.0 升级到 4.3.0
看起来像是为了升级 4.2.0 到 4.3.0 ,而误操作,给降级了
dubbo-dependencies-zookeeper-curator5。不是为了适应高版本zookeeper而做的依赖吗?我使用的就是zookeeper较高版本,因此依赖的是 dubbo-dependencies-zookeeper-curator5 而不是 dubbo-dependencies-zookeeper-curator
dubbo-dependencies-zookeeper-curator5。不是为了适应高版本zookeeper而做的依赖吗?我使用的就是zookeeper较高版本,因此依赖的是 dubbo-dependencies-zookeeper-curator5 而不是 dubbo-dependencies-zookeeper-curator
看了下应该是 dependentbot 升级 curator 依赖的时候错误升级了 curator5 模块的导致的
Will be fixed in https://github.com/apache/dubbo/pull/11492
thank you