Java 17 with Maven Wrapper results in Unrecognized VM option 'MaxPermSize=512m'

Question

I use OpenJDK 17 with Maven Wrapper 3.8.2 from Spring Initializr (Maven project, JAR packaging, Java 17, Spring Boot 2.6.0). No additional dependencies.

user@DESKTOP-U2OU5HG MINGW64 /c/Projects/my-project (master)
$ java -version
openjdk version "17" 2021-09-14
OpenJDK Runtime Environment (build 17+35-2724)
OpenJDK 64-Bit Server VM (build 17+35-2724, mixed mode, sharing)

Upon running any of ./mvnw.cmd -version or ./mvnw.cmd clean install, I always get the following message:

Unrecognized VM option 'MaxPermSize=512m'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Switching to OpenJDK 16.0.2 resolves the issue, however, I need to work with Java 17.

How to get it run? There is nowhere MaxPermSize=512m set.

Isn't this answers your question, https://stackoverflow.com/questions/47112412/unrecognized-vm-option-maxpermsize-512m-when-running-zeppelin . After Java9 it seems `MaxPermSize=512m` is removed. — Maneesha Indrachapa, Oct 01 '21 at 08:36
@JoachimSauer There is no `.mvn/jvm.config` file. Only `wrapper` folder. — Nikolas Charalambidis, Oct 01 '21 at 08:38
@ThorbjørnRavnAndersen: The only thing I switch is the home folder for Java 16 and 17 respectively. There is nothing set in my project as it is nearly empty and using downloaded Maven Wrapper. — Nikolas Charalambidis, Oct 01 '21 at 08:39
Yes. The newer JVM does not like a command option which comes from somewhere. You may want to single step your mvnw script. — Thorbjørn Ravn Andersen, Oct 01 '21 at 08:44
@ManeeshaIndrachapa even Java 8 does not support this option. — Holger, Oct 01 '21 at 14:53

Nikolas Charalambidis · Accepted Answer · 2022-06-10T02:25:42.827

34

Indeed -XX:MaxPermSize=size is labelled as follows according to Java® Development Kit Version 16/17 Tool Specifications (see the links):

For Java 16 it is obsolete.
For Java 17 it is removed.

The Maven Wrapper in the mvnw.cmd script, however, aside from the required JAVA_HOME, uses also a bunch of optional environment variables such as M2_HOME and these starting with MAVEN_ prefix.

The important one is MAVEN_OPTS where such a removed Java option can appear causing the inability to start the JVM on the newer version. In my case, I had something like:

MAVEN_OPTS="-Xmx4g -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"

The solution is either to remove the option from the environment variables or add this line to the Maven Wrapper script to override the MAVEN_OPTS value, In the minimal form:

MAVEN_OPTS=

edited Jun 10 '22 at 02:25

answered Oct 01 '21 at 09:02

Nikolas Charalambidis

40,893
16
117
183

1

for me (using Java 17), removing `-XX:MaxPermSize=512m` in pom.xml surefire configuration (`@{argLine} -Xmx1024m -XX:MaxPermSize=256m`), leaving me with `@{argLine} -Xmx1024m`, fixed my issues. – svassr Mar 31 '23 at 19:07
@svassr Yes, your case is luckily discoverable using the full-text search in the IDE. :) – Nikolas Charalambidis Apr 01 '23 at 12:39

Java 17 with Maven Wrapper results in Unrecognized VM option 'MaxPermSize=512m'

1 Answers1

Linked