我的应用程序有很多依赖项。一种依赖是 ActiveMQ Artemis。在 Maven 模块的 pom.xml 中,我将版本从 2.4.0 更新到 2.10.0
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>artemis-server</artifactId>
<version>2.10.0</version>
</dependency>
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>artemis-commons</artifactId>
<version>2.10.0</version>
</dependency>
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>artemis-jms-client-all</artifactId>
<version>2.10.0</version>
</dependency>
我用来启动 Artemis 经纪商的代码如下:
EmbeddedActiveMQ broker = new EmbeddedActiveMQ();
String fileConfig = "file:///" + brokerFile.getAbsolutePath();
broker.setConfigResourcePath(fileConfig);
代理客户端通过 Camel 的 sjms 组件连接:
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory cf = new ActiveMQJMSConnectionFactory(url);
SjmsComponent component = new SjmsComponent();
component.setConnectionFactory(cf);
context.addComponent("sjms", component);
我在另一个使用 Gradle 5.6.2 构建/编译的应用程序中使用这个 Maven 模块。该应用程序还包含 Apache Camel 2.24.2 和 Apache ActiveMQ 5.5.10 的库。
应用程序编译正常,但在运行时我收到“NoSuchMethodError”:
Handler dispatch failed; nested exception is java.lang.NoSuchMethodError: org.apache.activemq.artemis.utils.ClassloadingUtil.loadProperty(Ljava/lang/ClassLoader;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;
来自日志记录:
2019-09-21 03:03:00.883 WARN 4984 --- [ XNIO-2 task-14] .m.m.a.ExceptionHandlerExceptionResolver : Resolved exception caused by handler execution: org.springframework.web.util.NestedServletException: Handler dispatch failed; nested exception is java.lang.NoSuchMethodError: org.apache.activemq.artemis.utils.ClassloadingUtil.loadProperty(Ljava/lang/ClassLoader;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;
java.lang.NullPointerException
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.finalize(ActiveMQConnectionFactory.java:961)
at java.lang.System$2.invokeFinalize(System.java:1270)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:102)
at java.lang.ref.Finalizer.access$100(Finalizer.java:34)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:217)
基于文章修复NoSuchMethodErrors和NoSuchMethodExceptions的3个步骤我运行了“gradlew依赖项”。
| +--- org.apache.activemq:artemis-server:2.10.0 -> 2.4.0
| | +--- org.jboss.logging:jboss-logging:3.3.0.Final -> 3.3.2.Final
| | +--- org.apache.activemq:artemis-commons:2.4.0
| | | +--- org.jboss.logging:jboss-logging:3.3.0.Final -> 3.3.2.Final
| | | +--- io.netty:netty-buffer:4.1.16.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-transport:4.1.16.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-handler:4.1.16.Final -> 4.1.31.Final (*)
| | | +--- commons-beanutils:commons-beanutils:1.9.3
| | | | +--- commons-logging:commons-logging:1.2
| | | | \--- commons-collections:commons-collections:3.2.2
| | | \--- com.google.guava:guava:19.0 -> 25.1-jre (*)
| | +--- org.apache.activemq:artemis-selector:2.4.0
| | +--- org.apache.activemq:artemis-journal:2.4.0
| | | +--- org.jboss.logging:jboss-logging:3.3.0.Final -> 3.3.2.Final
| | | +--- org.apache.activemq:artemis-commons:2.4.0 (*)
| | | \--- org.apache.activemq:artemis-native:2.4.0
| | | \--- org.jboss.logging:jboss-logging:3.3.0.Final -> 3.3.2.Final
| | +--- org.apache.activemq:artemis-jdbc-store:2.4.0
| | | +--- org.jboss.logging:jboss-logging:3.3.0.Final -> 3.3.2.Final
| | | +--- org.apache.activemq:artemis-journal:2.4.0 (*)
| | | \--- org.apache.activemq:artemis-core-client:2.4.0
| | | +--- org.jgroups:jgroups:3.6.13.Final -> 3.6.7.Final
| | | +--- org.apache.activemq:artemis-commons:2.4.0 (*)
| | | +--- org.apache.johnzon:johnzon-core:0.9.5 -> 1.1.10
| | | +--- io.netty:netty-transport-native-epoll:4.1.16.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-transport-native-kqueue:4.1.16.Final -> 4.1.31.Final (*)
| | | \--- io.netty:netty-codec-http:4.1.16.Final -> 4.1.31.Final (*)
| | +--- org.apache.activemq:artemis-core-client:2.4.0 (*)
| | \--- io.netty:netty-all:4.1.16.Final -> 4.1.9.Final
| +--- org.apache.activemq:artemis-commons:2.10.0 -> 2.4.0 (*)
| +--- org.apache.activemq:artemis-jms-client-all:2.10.0
所以Artemis代理实际上运行在2.4.0版本下,而客户端运行在2.10.0版本下(使它们不兼容)。
我的文章指出:
“最后,我们需要决定我们实际上需要两个版本中的哪一个来满足这两个依赖关系。通常,这是较新的版本,因为大多数框架在某种程度上都向后兼容。但是,也可能是相反的情况,或者我们可能会这样做甚至根本无法解决冲突。”
为了强制两者在 2.10.0 上运行,我在 build.gradle 文件中明确声明:
configurations.all {
resolutionStrategy {
force 'org.apache.activemq:artemis-core-client:2.10.0', 'org.apache.activemq:artemis-broker:2.10.0','org.apache.activemq:artemis-commons:2.10.0','org.apache.activemq:artemis-selector:2.10.0','org.apache.activemq:artemis-journal:2.10.0'
}
}
compile group: 'org.apache.activemq', name: 'artemis-core-client', version: '2.10.0'
compile group: 'org.apache.activemq', name: 'artemis-commons', version: '2.10.0'
compile group: 'org.apache.activemq', name: 'artemis-server', version: '2.10.0'
compile group: 'org.apache.activemq', name: 'artemis-selector', version: '2.10.0'
compile group: 'org.apache.activemq', name: 'artemis-journal', version: '2.10.0'
在此“gradlew依赖项”之后:
| +--- org.apache.activemq:artemis-server:2.10.0
| | +--- org.jboss.logging:jboss-logging:3.4.0.Final -> 3.3.2.Final
| | +--- org.jboss.logmanager:jboss-logmanager:2.1.10.Final
| | | \--- org.wildfly.common:wildfly-common:1.5.1.Final
| | +--- org.apache.activemq:artemis-commons:2.10.0
| | | +--- org.jboss.logging:jboss-logging:3.4.0.Final -> 3.3.2.Final
| | | +--- io.netty:netty-buffer:4.1.34.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-transport:4.1.34.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-handler:4.1.34.Final -> 4.1.31.Final (*)
| | | \--- commons-beanutils:commons-beanutils:1.9.3
| | | +--- commons-logging:commons-logging:1.2
| | | \--- commons-collections:commons-collections:3.2.2
| | +--- org.apache.activemq:artemis-selector:2.10.0
| | | \--- org.apache.activemq:artemis-commons:2.10.0 (*)
| | +--- org.apache.activemq:artemis-journal:2.10.0
| | | +--- org.jboss.logging:jboss-logging:3.4.0.Final -> 3.3.2.Final
| | | +--- org.apache.activemq:artemis-commons:2.10.0 (*)
| | | +--- org.apache.activemq:activemq-artemis-native:1.0.0
| | | | +--- org.jboss.logging:jboss-logging:3.3.1.Final -> 3.3.2.Final
| | | | \--- org.jboss.logmanager:jboss-logmanager:2.0.3.Final -> 2.1.10.Final (*)
| | | +--- io.netty:netty-buffer:4.1.34.Final -> 4.1.31.Final (*)
| | | \--- io.netty:netty-common:4.1.34.Final -> 4.1.31.Final
| | +--- org.apache.activemq:artemis-jdbc-store:2.10.0
| | | +--- org.jboss.logging:jboss-logging:3.4.0.Final -> 3.3.2.Final
| | | +--- org.apache.activemq:artemis-commons:2.10.0 (*)
| | | +--- org.apache.activemq:artemis-journal:2.10.0 (*)
| | | \--- org.apache.activemq:artemis-core-client:2.10.0
| | | +--- org.jgroups:jgroups:3.6.13.Final -> 3.6.7.Final
| | | +--- org.apache.activemq:artemis-commons:2.10.0 (*)
| | | +--- org.apache.johnzon:johnzon-core:0.9.5 -> 1.1.10
| | | +--- io.netty:netty-transport-native-epoll:4.1.34.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-transport-native-kqueue:4.1.34.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-codec-http:4.1.34.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-buffer:4.1.34.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-transport:4.1.34.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-handler:4.1.34.Final -> 4.1.31.Final (*)
| | | +--- io.netty:netty-codec:4.1.34.Final -> 4.1.31.Final (*)
| | | \--- io.netty:netty-common:4.1.34.Final -> 4.1.31.Final
| | +--- org.apache.activemq:artemis-core-client:2.10.0 (*)
| | +--- org.apache.activemq:activemq-artemis-native:1.0.0 (*)
问题
代理和客户端库都处于同一版本,并且应用程序似乎工作正常。然而这让我感到不安:
force
、配置级别 force
或替换规则来实现。您的构建中有些东西使用其中一种技术来强制降低版本。dependencyInsight
任务获取有关为何选择特定版本模块的更详细报告。
类似 ./gradlew dependencyInsight --configuration <relevantConfiguration> --dependency artemis-server
的内容,其中 <relevantConfiguration>
可以是 compileClasspath
或 runtimeClasspath
或者更具体到您的项目的内容。2.10.0
降级为 2.4.0
,您也许可以使用与 force
不同的解决方案来获得您期望的版本。