Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
5.0-alpha1, 5.0, 5.1
-
None
-
Packaging - Package Distribution
-
Critical
-
Low Hanging Fruit
-
Adhoc Test
-
None
-
Description
The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the corresponding redhat/cassandra.in.sh was not.
This means when cassandra starts on a rpm install using jdk17 the jvm11-server.options file is still used. And so it fails.
Initial patch that works: https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0
Maybe it is possible to find a superior solution, like wrapping this file instead of duplicating it.
Attachments
Issue Links
- is caused by
-
CASSANDRA-18255 Drop JDK8 Support
- Resolved