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

Configuring JVM Settings for Minecraft

  • 3.2K Views
  • Last Post 15 April 2018
  • Topic Is Solved
0xTrace posted this 15 April 2018

AMP ver: 1.6.0 & Nightly builds

Module: Minecraft

Issue: I've been having issues with AMP's management of the JVM settings. Since upgrading to 1.6.0, I've noticed that my custom JVM arguments are not being saved properly. It appears that when setting the JVM arguments either through the web portal or in the MinecraftModule.kvp file, AMP does not include a necessary space at the end of the arguments. I can work around this by manually adding a space and starting the server; however, this negates any unattended use of AMP. I've also found that the Nightly build is affected by this as well.

Additionally, when I use the following arguments, AMP will not start the server since Java throws a conflicting collector arguments error.

-Xms1g -Xmx4g -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=348m -XX:+UseG1GC -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32

Which leads me to believe that AMP is pre-loading some arguments elsewhere; however, I have not been able to identify where those arguments are being read from. I've modified the FTB ServerStart.sh file (since I'm on linux) and, just in case, I've even modified the ServerStart.bat file. Both changes did not affect AMP's hidden arguments. The MinecraftModule.kvp file also has the same line; but -XX:+UseParNewGC still seems to find its way, despite that I've removed any reference from the usual places.

Beyond the files that I listed (MinecraftModule.kvp & ServerStart.sh), are there any other locations where AMP reads in JVM arguments?

Order By: Standard | Newest | Votes
Mike posted this 15 April 2018

Upgrade to nightly which adds the space correctly. Although you'll end up with duplicate arguments if you leave Xmx in since AMP specifies that by default. Failing that use the 'Custom' option.

0xTrace posted this 15 April 2018

Thank you for the reply.

I'll try another round with the Nightly builds for the space issue with the custom JVM options.

Aside from the -Xmx parameter, are there any other JVM parameters that are hard coded into AMP for the MinecraftModule?

Mike posted this 15 April 2018

if you're using the Custom server type then it has zero arguments other than the custom ones supplied in the advanced settings, otherwise it depends on the server type. The 'official' type has nothing other than the jar file and Xmx so it's a good starting point.

Close