[
https://issues.apache.org/jira/browse/CASSANDRA-19001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782914#comment-17782914
]
Ekaterina Dimitrova commented on CASSANDRA-19001:
-------------------------------------------------
Related information, mentioned also in the release vote thread:
{code:java}
Hi Paulo,
Thank you for testing and for raising the issue!
I can confirm I do not use the same JDK as you, and I did not see any
warnings on my machine on startup or when calling nodetool commands.
I believe on a quick check that jdk.attach was needed for nodetool sjk. (It
was mentioned on CASSANDRA-16895 at least)
About jdk.compiler - it was added as per this recommendation for chronicle
https://chronicle.software/chronicle-support-java-17/
I do not believe we test with the mentioned JDK in CI, so additional
testing will be required to figure out things better.
As this is alpha release - can we open a ticket to be resolved in the
next alpha/beta? It is up to PMC to decide, of course. Also, we need a bit
more investigation here. I can try to take a look tomorrow in more
detail if no one beats me to that.
Best regards,
Ekaterina{code}
{code:java}
I am sorry, I totally forgot to address your other concern, Paulo. The
security manager is marked for deprecation in JDK 17. So this warning is to
stress to people they need to take care of a replacement, sooner than
later. I believe we have somewhere an unassigned ticket in Open status to
address this topic.
{code}
> Check whether the startup warnings for unknown modules represent a legit
> problem or cosmetic issue
> --------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19001
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19001
> Project: Cassandra
> Issue Type: Bug
> Components: Build
> Reporter: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 5.0-beta
>
>
> During the 5.0 alpha 2 release
> [vote|https://lists.apache.org/thread/lt3x0obr5cpbcydf5490pj6b2q0mz5zr],
> [~paulo] raised the following concerns:
>
> {code:java}
> Launched a tarball-based 5.0-alpha2 container on top of
> "eclipse-temurin:17-jre-focal" and the server starts up fine, can run
> nodetool and cqlsh.
> I got these seemingly harmless JDK17 warnings during startup and when
> running nodetool (no warnings on JDK11):
> WARNING: Unknown module: jdk.attach specified to --add-exports
> WARNING: Unknown module: jdk.compiler specified to --add-exports
> WARNING: Unknown module: jdk.compiler specified to --add-opens
> WARNING: A terminally deprecated method in java.lang.System has been called
> WARNING: System::setSecurityManager has been called by
> org.apache.cassandra.security.ThreadAwareSecurityManager
> (file:/opt/cassandra/lib/apache-cassandra-5.0-alpha2-SNAPSHOT.jar)
> WARNING: Please consider reporting this to the maintainers of
> org.apache.cassandra.security.ThreadAwareSecurityManager
> WARNING: System::setSecurityManager will be removed in a future release
> Anybody knows if these warnings are legit/expected ? We can create
> follow-up tickets if needed.
> $ java --version
> openjdk 17.0.9 2023-10-17
> OpenJDK Runtime Environment Temurin-17.0.9+9 (build 17.0.9+9)
> OpenJDK 64-Bit Server VM Temurin-17.0.9+9 (build 17.0.9+9, mixed mode,
> sharing)
> {code}
> {code:java}
> Clarification: - When running nodetool only the "Unknown module" warnings
> show up. All warnings show up during startup.{code}
> We need to verify whether this presents a real problem in the features where
> those methods are expected to be used or it is a false alarm.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
