Ubuntu 16.04 + Neo4j v3.0.1 -- installation via apt-get pulls in Java 9 #7188
Comments
|
Something is very odd about this. Java9 is not released and should only exist in experimental sources. Could you post the output |
|
@spacecowboy - Running that in the terminal doesn't work for me (perhaps I'm running it incorrectly?): I have only a single |
|
yes, but you might also have more What I was trying to ascertain was whether you something strange there from where java9 might come from. Some googling around seems to indicate that Xenial Xerus actually ships openjdk-9 available by default however, so no error on your part. Thanks for the report, we'll sort this out.. Meanwhile, it should be fine if you split it into two steps: |
|
I can confirm that installing |
|
This appears to be a bug in Ubuntu, see this for example: Our debian package explicitly requires |
|
Also reported to Ubuntu now: |
The Ubuntu 16.04 repos include Java 9, despite its not having been released yet (see https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1584118). Because the Java 9 package provides java8-runtime, this results in Java 9 being installed by default when people install our package on Ubuntu 16.04. This causes problems because: * We are not compatible with Java 9 because there is a change in command line argument order and the JVM fails to start. * We don't support Java 9 and have not tested against it. This change adds makes our package conflict with Java 9, so Java 8 is installed instead. Fixes neo4j#7188.
The Ubuntu 16.04 repos include Java 9, despite its not having been released yet (see https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1584118). Because the Java 9 package provides java8-runtime, this results in Java 9 being installed by default when people install our package on Ubuntu 16.04. This causes problems because: * We are not compatible with Java 9 because there is a change in command line argument order and the JVM fails to start. * We don't support Java 9 and have not tested against it. This change adds makes our package conflict with Java 9, so Java 8 is installed instead. Fixes neo4j#7188.
|
@MysterAitch The fix for this will be in Neo4j 3.0.2. |
|
I'm seeing the same issue with the |
|
Also the Ubuntu report appears to have been updated recently suggesting a different approach to fixing this issue than the one currently queued for release. |
|
@mal thanks for the notice. I have commented on the ubuntu issue why that doesn't work. |
|
FYI for anyone else experiencing this in the interim, it's possible to work around the issue like this: Tested for neo4j (2.2.7, 2.2.10) on ubuntu 16.04 |
|
Another workaround is to manually install java8 before neo4j as I mention above, although your solution is a system wide solution which also fixes the issue for other packages |
|
Aha, you're quite correct. I arrived at the pinning solution after trying to install |
|
yes we have an independent issue that we depend on |
|
@mal we have backported this to 2.2 and 2.3 now. |
|
Excellent! Thanks @spacecowboy, very much appreciated Do you happen to know when they'll make their way into |
|
@mal next patch release I'm afraid :( |
|
all temporary solutions mentioned here do not work for me (ubuntu 12.04). |
|
@biganfa What version of Neo4j are you installing? |
|
@biganfa that's quite surprising since ubuntu 12.04 doesn't have java9 in its default repos. What extra repos/ppas have you enabled? |
|
@benbc @spacecowboy i did not do anything special, just typed |
|
Hello, I have many java version installed on my ubuntu system, as different applications require different java versions. I solved the issue by adding the following line at the beginning of /etc/neo4j/neo4j.conf:
After this it worked and I was able to connect to the web service... |
Per a conversation via Slack, here is an issue describing my installation experience today .
In particular, note that the standard apt-get installation of neo4j is pulling in
openjdk-9-jreandopenjdk-9-jre-headless.This was discovered because the neo4j service would not start, per this:
The text was updated successfully, but these errors were encountered: