[jira] [Updated] (CASSANDRA-16485) Cassandra 3.11.2 not compatible with Oracle JRE 1.8.0_281

["Brandon Williams (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-16485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-16485:
-----------------------------------------
    Resolution: Invalid
        Status: Resolved  (was: Triage Needed)

This jira is for bug tracking, not support. 3.11.2 has long since sailed but your problem looks generically rooted in JNA, and nothing the project could solve anyway.  I recommend contacting the user list or slack for troubleshooting: https://cassandra.apache.org/community/

> Cassandra 3.11.2 not compatible with Oracle JRE 1.8.0_281
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-16485
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16485
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Arun Karunakaran
>            Priority: Normal
>         Attachments: debug.log, system.log
>
>
> In our environments, we need to patch with latest JRE when Oracle release its quarterly critical patch update.
> We are running Teamwork cloud 19.0 SP4 and Cassandra 3.11.2 which is using JRE 1.8.0_251 at the moment.
> All Java critical patch update after 251 seem to be incompatible with Cassandra . Latest Java 8 Update 281 is also not compatible .
> When Cassandra windows service is started with latest Java 8 Update 281 installed , service does not start . Error is thrown in system and debug log files(Refer attached)
> Please advise on how to keep the environment patched with latest update and also have cassandra running .



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org