30

When I try to run Zeppelin by either

bin/zeppelin.sh

or

bin/zeppelin-deamon.sh start

I was getting the following error message.

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

Java 9 is installed on my system (Ubuntu 16.04).

$ java -version                         
openjdk version "9-internal"
OpenJDK Runtime Environment (build 9-internal+0-2016-04-14-195246.buildd.src)
OpenJDK 64-Bit Server VM (build 9-internal+0-2016-04-14-195246.buildd.src, mixed mode)
MichaelChirico
  • 33,841
  • 14
  • 113
  • 198
sbbs
  • 1,450
  • 2
  • 13
  • 20
  • 2
    You appear to have an ancient build of JDK 9 on your system. The JDK 9 GA build reports itself as "9", released September 2017. Your build seems to be from early 2016. In any case, the MaxPermSize option only make sense with JDK 7 and older releases. With JDK 8 and JDK 9 you will get a warning like this: "ignoring option MaxPermSize=128m; support was removed in 8.0". One final point - if zeppelin have an issue tracker then it would be good to submit a bug so that they know to update their scripts. – Alan Bateman Nov 04 '17 at 15:55
  • Yeah, it does look like an ancient version. `openjdk-9-jdk` series was installed on my system, and I removed them. – sbbs Nov 04 '17 at 16:29
  • Does this answer your question? [Android Studio - Unrecognized VM option 'MaxPermSize=256m'](https://stackoverflow.com/questions/31411989/android-studio-unrecognized-vm-option-maxpermsize-256m) – Mahozad Nov 07 '21 at 12:18

4 Answers4

24

It appears the MaxPermSize VM option is no longer supported in Java 9. Perhaps they changed the parameter name or something. Instead of digging into this issue further, as I had no particular reason to insist on using Java 9, I installed Java 8 as follows:

sudo apt install openjdk-8-jdk

And made it a default Java environment

sudo update-alternatives --config java

This fixed the issue.

sbbs
  • 1,450
  • 2
  • 13
  • 20
14

If anyone still getting this renaming MaxPermSize to MaxMetaspaceSize fixed the issue on my part, migrated from gradle7.2 to gradle8 with jdk11 previously, now on jdk17

lgmg
  • 141
  • 1
  • 2
2

Check your gradle.properties

I had this line in it

org.gradle.jvmargs=-Xmx4g -XX:MaxPermSize=2g -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8

removed it and everything works like charm :)

Maulzey
  • 4,100
  • 5
  • 22
  • 30
0

Maybe this could answer your question: https://stackoverflow.com/a/12114284/3957538

You don't need to remove the full line as @Maulzey said.

Instead, just remove MaxPermSize or use it respective sustitution.