Project

General

Profile

Bug #7345

JVM 8.0: warning about "Ignoring option PermSize=128m; support was removed in 8.0"

Added by David Durieux over 5 years ago. Updated about 4 years ago.

Status:
Released
Priority:
4
Category:
System integration
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

There is a warning and I think it can be a problem:

Starting Jetty: OpenJDK 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

Related issues

Related to Rudder - Bug #7348: rudder-jetty initialisation should not support Java 6ReleasedBenoît PECCATTE2015-11-02Actions
#1

Updated by Jonathan CLARKE over 5 years ago

  • Subject changed from Centos 7.1 to JVM 8.0: Ignoring options MaxPermSize/PermSize=128m; support was removed in 8.0
#2

Updated by François ARMAND over 5 years ago

It's not a problem, in the sense that the JVM is only warning us that we are using a deprecated parameter in its starting option. The corresponding option is now enterilly managed by the JVM and the OS.

But clearly, we should have a way to avoid the warning, that may be frightning - and well, have a soft starting with "warning" is not the best we can hope for :)

So, we need some way to add the "MaxPermSize/PermSize" option only when the installed JVM version (or more preciselly, the JVM version used for starting the webapp) is < 8.0. Certainly, it should be in the init script.

#3

Updated by Jonathan CLARKE over 5 years ago

  • Subject changed from JVM 8.0: Ignoring options MaxPermSize/PermSize=128m; support was removed in 8.0 to JVM 8.0: warning about "Ignoring option PermSize=128m; support was removed in 8.0"
  • Priority changed from N/A to 4
#4

Updated by Jonathan CLARKE over 5 years ago

  • Category set to System integration
  • Status changed from New to In progress
  • Assignee set to Jonathan CLARKE
  • Target version set to 2.10.20

We should detect JVM version and only use these options if JVM version < 1.8.

#5

Updated by Jonathan CLARKE over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/773
#6

Updated by Jonathan CLARKE over 5 years ago

  • Related to Bug #7348: rudder-jetty initialisation should not support Java 6 added
#7

Updated by Jonathan CLARKE over 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
#9

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.20, 2.11.17, 3.0.12 and 3.1.5 which were released today.

#10

Updated by Benoît PECCATTE about 4 years ago

  • Found in version (s) 3.1.2 added
#11

Updated by Benoît PECCATTE about 4 years ago

  • Found in version(s) old deleted (3.1.2)

Also available in: Atom PDF