[
https://issues.apache.org/jira/browse/CASSANDRA-18817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-18817:
-------------------------------------------
Fix Version/s: 5.0
5.0-alpha1
5.1
(was: 5.0-alpha)
Since Version: 5.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/17d0eb138c69a1c9c44256695252b2d2213a2633
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed as
[17d0eb138c69a1c9c44256695252b2d2213a2633|https://github.com/apache/cassandra/commit/17d0eb138c69a1c9c44256695252b2d2213a2633].
> RPM install does not work with jdk17
> ------------------------------------
>
> Key: CASSANDRA-18817
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18817
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Reporter: Michael Semb Wever
> Priority: Normal
> Fix For: 5.0, 5.0-alpha1, 5.1
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
