>
>
>
> at least 3.0.14 starts up fine for me with 8u162.
>
>
>
> Regards,
>
> Thomas
>
>
>
> *From:* Ben Wood [mailto:bw...@mesosphere.io]
> *Sent:* Donnerstag, 18. Jänner 2018 23:24
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: Cassandra 3.11
Ben,
at least 3.0.14 starts up fine for me with 8u162.
Regards,
Thomas
From: Ben Wood [mailto:bw...@mesosphere.io]
Sent: Donnerstag, 18. Jänner 2018 23:24
To: user@cassandra.apache.org
Subject: Re: Cassandra 3.11 fails to start with JDK8u162
I'm correct in assuming 10091 didn't go into 3.0
m:* li...@beobal.com [mailto:li...@beobal.com] *On Behalf Of *Sam
> Tunnicliffe
> *Sent:* Donnerstag, 18. Jänner 2018 10:16
> *To:* user@cassandra.apache.org
> *Subject:* Re: Cassandra 3.11 fails to start with JDK8u162
>
>
>
> This isn't (wasn't) a known issue, but the way th
Sam,
thanks for the confirmation. Going back to u152 then.
Thomas
From: li...@beobal.com [mailto:li...@beobal.com] On Behalf Of Sam Tunnicliffe
Sent: Donnerstag, 18. Jänner 2018 10:16
To: user@cassandra.apache.org
Subject: Re: Cassandra 3.11 fails to start with JDK8u162
This isn't (wasn't
This isn't (wasn't) a known issue, but the way that CASSANDRA-10091 was
implemented using internal JDK classes means it was always possible that a
minor JVM version change could introduce incompatibilities (CASSANDRA-2967
is also relevant).
We did already know that we need to revisit the way this
Thank you Thomas for starting this thread, I'm having exactly the same
issue on AWS EC2 RHEL-7.4_HVM-20180103-x86_64-2-Hourly2-GP2 (ami-dc13a4a1)
I was starting to bang my head on my desk !
So I'll try to downgrade back to 152 then !
On 18 January 2018 at 08:34, Steinmaurer, Thomas <
