You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2017/06/12 07:52:00 UTC

[jira] [Resolved] (KARAF-5196) Strongly consider removing -XX:+UnsyncloadClass from start scripts

     [ https://issues.apache.org/jira/browse/KARAF-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved KARAF-5196.
-----------------------------------------
    Resolution: Fixed

> Strongly consider removing -XX:+UnsyncloadClass from start scripts
> ------------------------------------------------------------------
>
>                 Key: KARAF-5196
>                 URL: https://issues.apache.org/jira/browse/KARAF-5196
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 4.1.1
>            Reporter: Holger Hoffstätte
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.2.0, 4.1.2
>
>
> I was just very confused when I saw that a customer JVM was running with -XX:+UnsyncloadClass active; I always run with proper JAVA_OPTS so I never saw it before. This flag is very questionable and even has its own JDK bug: https://bugs.openjdk.java.net/browse/JDK-8140284
> Please consider removing it from the default scripts. Even if there is/was a valid reason it seems questionable to rely on it, considering what it does.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)