Bug #7345: JVM 8.0: warning about "Ignoring option PermSize=128m; support was removed in 8.0" - Rudder - Issue Tracker

Actions

Copy link

Bug #7345

closed

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

Added by David Durieux about 9 years ago. Updated over 7 years ago.

Status:

Released

Priority:

Assignee:

Benoît PECCATTE

Category:

System integration

Target version:

2.10.20

Pull Request:

https://github.com/Normation/rudder-p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

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 1 (0 open — 1 closed)

Actions

Copy link

Updated by Jonathan CLARKE about 9 years ago

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

Actions

Copy link

Updated by François ARMAND about 9 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.

Actions

Copy link

Updated by Jonathan CLARKE about 9 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