Forums Archived

This forum has been archived. No new posts can be made and no new users can sign up. It remains here for reference only.

Find the new forums here

Unable to detect Java, PATH and installs are all correct.

  • 576 Views
  • Last Post 23 December 2021
selin posted this 19 December 2021

OS Name/Version: OS Name Microsoft Windows 10 Pro Version 10.0.19042 Build 19042

Product Name/Version: AMP Release "Triton" v2.3.0.6, built 02/12/2021 15:36

Problem Description: After attempting to swap a Minecraft server network from Bungeecord 1.17.1 to Waterfall 1.8.8, I swapped from JDK16 to JDK 17. I went through the usual uninstall and reinstall process and triple checked that OpenJDK17U-jdkx64windowshotspot17.0.1_12 was the only java version installed on the system other than jre-8u311, as well as that the PATH variables were all correct. However, my instances and AMP continue to fail to recognize any java versions installed on the system and refuse to run.

Steps to reproduce: 0.) Had previous jre-8u311 and older AMP versions installed.

1.) Updated AMP to AMP Release "Triton" v2.3.0.6, built 02/12/2021 15:36
2.) Uninstalled JDK16 and installed OpenJDK17U-jdkx64windowshotspot17.0.1_12
3.) double checked that PATH variables were correct, yet AMP would not recognize even through multiple install and restart attempts.

Order By: Standard | Newest | Votes
AbhorrentJoel posted this 19 December 2021

I'm not 100% sure, but I have a feeling this may be an issue addressed in the latest Nightly build. Mike would be able to confirm for sure since I am not using the Nightly build.

You could try to switch to the Nightly build using the following command:

ampinstmgr switch INSTANCENAME Nightly

If it works, I would suggest keeping to the Nightly until the next MainLine release comes out since downgrading is probably more likely to cause issues. You can switch back to the MainLine using the following:

ampinstmgr switch INSTANCENAME MainLine True

Obviously change the INSTANCENAME with the instance you wish to switch to Nightly. You may also need to switch the ADS to Nightly in some cases due to version mismatching.

selin posted this 23 December 2021

I tried this and currently it's throwing an error talking about a Java version mismatch.

Unsupported Java detected (61.0). Only up to Java 16 is supported.

AbhorrentJoel posted this 23 December 2021

2.3.0.8 has been released if you're wanting to jump back into MainLine.

Which Java versions do you see in the Java settings for the instance? AMP is attempting execute using Java 17 (61.0) but the server needs to use Java 16 (60.0) or older.

Please let me know if I'm missing something.

Close