-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to start EmbeddedCassandra with JAVA 11 #294
Comments
I am getting something like this when I try to switch to jdk11 from jdk8: |
There is a PR that attempts to fix this I believe: |
along with the discussion: #249 |
When is this getting fixed, i also updated to java11 and embedded server fails to come up |
I am also facing the same issue after updating to Java 11. Any updates on when this will be fixed? |
Any idea When is this going to be fixed |
Looks like Cassandra Unit isn't compatible with Java 11 jsevellec/cassandra-unit#294
@jsevellec any update on this . This has been pending from a long time. |
I would like to have an update as well. |
+1 |
Any updates? |
@jsevellec Any updates on this? Cassandra Unit does not work on any Java version after Java 8 - which also happens to reach End of Life December 2020. There is a PR #282 that claims to resolve the issue that has sat open for almost 2 years. Similar issues |
Hi Guys, I'm sorry to hear that. Which version of cassandra-unit are you using? The latest version of cassandra-unit is 4.3.1.0 and is built and tested with java 11... Is this issue still here with this latest version? |
Yes, it is in the latest version. I have just re-verified it using cassandra-unit 4.3.1.0. I get the same exception as in the original post and I get it when running in Windows or a Windows disk mapped to a Linux virtual machine. It seems to work fine when running in Linux on a local disk. |
Is this issue the same as #283 ? |
Yes it is. It's the combo windows FS + Java 11 |
And since PR #282 was mentioned to possibly fix this I tried applying the latest Jamm version as well. That does not solve the problem. |
@jsevellec It looks to be an issue with dependency versions and Spring Boot.
Cassandra Unit 4 looks like it uses the Edit: looks like Spring Boot 2.3.0 will use the 4.x driver. https://spring.io/blog/2020/05/15/spring-boot-2-3-0-available-now |
Cassandra-unit fail since spring-boot 2.2.X where datastax driver was 3.X version, just in spring-boot 2.3.X they upgrade the driver version. The problem with this issue always was using java 11 on windows platforms with 2.2.X spring versions Regards |
CassandraUnit 4.3.1.0 runs an embedded Cassandra 3.11.5. Cassandra 3 requires Java 8. How could CassandraUnit work with Java 11 ? |
Any chance this might be resolved in this decade? Can we help? |
Csssandra 4 is expected within a month from now |
This commit depends on cassandra 4 rc1 which should be updated when the final release comes out These changes are verified against java 8 AND 11, but in order to run the tests, you must specify -Djdk.version=1.8 or -Djdk.version=11 depending on which version of java your maven is executing with Users of cassandra-unit will need to provide additional jvm args to their test runtime if they are running on java 11 as specified on pom.xml#165. this is due to a requirement of cassandra 4 (see https://github.com/apache/cassandra/blob/trunk/conf/jvm11-server.options#L59 for the default start script for cassandra4 on jvm11)
I have a PR of this lib working with the cassandra 4 RC1: #325 |
+1 |
1 similar comment
+1 |
I'm getting a error when embedded cassandra start after upgrade my project to Java 11, otherwise with Java 1.8 works perfectly .
Here my configuration:
My dependencies:
<cassandra-unit-spring.version>3.11.2.0</cassandra-unit-spring.version>
And the error I get is:
Do you have any clue what could be?
The text was updated successfully, but these errors were encountered: