Jump to content

Debian 10 - eraserver.service not using appropriate java version

Go to solution Solved by Taavi Ansper,

Recommended Posts

I have upgraded my java to java17 to use that with eraserver. Unfortunately some part of the scheme does not use the java version set by update-alternatives.

As you can see I have set to use the java 17 version.

root@eset:~# update-alternatives --config java
There are 3 choices for the alternative java (providing /usr/bin/java).

  Selection    Path                                            Priority   Status
  0            /usr/lib/jvm/java-11-openjdk-amd64/bin/java      1111      auto mode
  1            /usr/lib/jvm/java-11-openjdk-amd64/bin/java      1111      manual mode
* 2            /usr/lib/jvm/java-17-oracle/bin/java             1091      manual mode
  3            /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java   1081      manual mode

When restarting my systemd service. It still boots up the eraserver with java 11.

Has anyone had this issue?

Link to comment
Share on other sites

  • Solution

Seems I got it fixed. My JAVA_HOME was pointing to a wrong directory. After changing it in bashrc to the proper location and restarting the eraserver and eraserver-xvdb service it now uses Java 17.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...