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


On Fri, 3 Nov 2023 at 20:01, Paulo Motta <pa...@apache.org> wrote:

> Clarification:
> - When running nodetool only the "Unknown module" warnings show up. All
> warnings show up during startup.
>
> On Fri, Nov 3, 2023 at 7:58 PM Paulo Motta <pa...@apache.org> wrote:
>
>> 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)
>>
>> On Fri, Nov 3, 2023 at 6:13 PM Jonathan Ellis <jbel...@gmail.com> wrote:
>>
>>> +1
>>>
>>> On Mon, Oct 30, 2023 at 3:47 PM Mick Semb Wever <m...@apache.org> wrote:
>>>
>>>> Proposing the test build of Cassandra 5.0-alpha2 for release.
>>>>
>>>> DISCLAIMER, this alpha release does not contain the features:
>>>> Transactional Cluster Metadata (CEP-21) and Accord Transactions
>>>> (CEP-15).  These features are under discussion to be pushed to a
>>>> 5.1-alpha1 release, with an eta still this year.
>>>>
>>>> This release does contain Vector Similarity Search (CEP-30).
>>>>
>>>> Please also note that this is an alpha release and what that means,
>>>> further info at
>>>> https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle
>>>>
>>>> sha1: ea76d148c374198fede6978422895668857a927f
>>>> Git: https://github.com/apache/cassandra/tree/5.0-alpha2-tentative
>>>> Maven Artifacts:
>>>>
>>>> https://repository.apache.org/content/repositories/orgapachecassandra-1317/org/apache/cassandra/cassandra-all/5.0-alpha2/
>>>>
>>>> The Source and Build Artifacts, and the Debian and RPM packages and
>>>> repositories, are available here:
>>>> https://dist.apache.org/repos/dist/dev/cassandra/5.0-alpha2/
>>>>
>>>> The vote will be open for 72 hours (longer if needed). Everyone who
>>>> has tested the build is invited to vote. Votes by PMC members are
>>>> considered binding. A vote passes if there are at least three binding
>>>> +1s and no -1's.
>>>>
>>>> [1]: CHANGES.txt:
>>>>
>>>> https://github.com/apache/cassandra/blob/5.0-alpha2-tentative/CHANGES.txt
>>>> [2]: NEWS.txt:
>>>> https://github.com/apache/cassandra/blob/5.0-alpha2-tentative/NEWS.txt
>>>>
>>>
>>>
>>> --
>>> Jonathan Ellis
>>> co-founder, http://www.datastax.com
>>> @spyced
>>>
>>

Reply via email to