You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2022/06/02 13:08:00 UTC
[jira] [Updated] (IGNITE-17079) Fix compatibility framework when a node is started in a dedicated JVM with incorrect classpath
[ https://issues.apache.org/jira/browse/IGNITE-17079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-17079:
-------------------------------------
Issue Type: Bug (was: Task)
> Fix compatibility framework when a node is started in a dedicated JVM with incorrect classpath
> ----------------------------------------------------------------------------------------------
>
> Key: IGNITE-17079
> URL: https://issues.apache.org/jira/browse/IGNITE-17079
> Project: Ignite
> Issue Type: Bug
> Reporter: Maxim Muzafarov
> Assignee: Maxim Muzafarov
> Priority: Major
> Fix For: 2.14
>
>
> The classpath for a node builds incorrectly in case of groupId is missed.
> {code}
> 13:02:03 [2022-06-01 13:02:03,835][INFO ][Thread-33][jvm-ffce025a#2_13_0] Exception in thread "main" java.lang.AssertionError: Node is of unexpected version: [act=2.14.0#20220601-sha1:00000000, exp=2.13.0#19700101-sha1:00000000]
> 13:02:03 [2022-06-01 13:02:03,835][INFO ][Thread-33][jvm-ffce025a#2_13_0] at org.apache.ignite.compatibility.testframework.junits.IgniteCompatibilityNodeRunner.main(IgniteCompatibilityNodeRunner.java:104)
> 13:02:30 [2022-06-01 13:02:30,930][INFO ][Thread-33][jvm-ffce025a#2_13_0] Ignite startup/Init closure/post configuration closure is probably hanging at
> 13:02:30 [2022-06-01 13:02:30,931][INFO ][Thread-33][jvm-ffce025a#2_13_0]
> 13:02:30 [2022-06-01 13:02:30,931][INFO ][Thread-33][jvm-ffce025a#2_13_0] Dumping classpath
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)