[CASSANDRA-18431] Cassandra doesn't start on JDK17

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0
• Component/s: Build
• Epic Link: Support Java 17
• Bug Category: Correctness
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/d1d733bee5ba85088a77d5c1430705dbb47ab68c https://github.com/apache/cassandra/commit/c3874624853f5a734a7751965baa9c28e0c83bfd

Test and Documentation Plan

Patch, CI

ninja fix, CI

• Assignee: Ekaterina Dimitrova
• Reporter: Ekaterina Dimitrova

Authors

Ekaterina Dimitrova

Reviewers

Ekaterina Dimitrova, Michael Semb Wever

• Created: 05/Apr/23 19:44
• Updated: 12/Sep/23 13:02
• Resolved: 06/Apr/23 19:06

Description

CASSANDRA-17199 added a new call to jamm measureDeep which hits some JDK internals and prevents us from starting Cassandra with JDK17. This will be solved with CASSANDRA-18329.

Until new version of jamm lands we can workaround the problem either by adding add-opens or by replacing temporarily

public static final long IPV6_SOCKET_ADDRESS_SIZE = ObjectSizes.measureDeep(new InetSocketAddress(getIpvAddress(16), 42));

with

public static final long IPV6_SOCKET_ADDRESS_SIZE = 168;

measured with JOL.

Then we can switch back to the current call here later.

Issue Links

• blocks: CASSANDRA-17869 Add JDK17 option to cassandra-builds (build-scripts and jenkins dsl) and on jenkins agents
• is caused by: CASSANDRA-17199 Provide summary of failed SessionInfo's in StreamResultFuture