[jbosstools-issues] [JBoss JIRA] (JBIDE-20292) Remove MaxPermSize from server scripts when Java 9 is used

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-20292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090198#comment-13090198 ] 

Rob Stryker commented on JBIDE-20292:
-------------------------------------

This task is impossible to accomplish until there exists a java9 execution environment. As of now there's really no real way for me to figure out that a java9 vm is actually java 9, at least not through the interfaces.   In the past, I dug further to try to see how they actually get the java version from various jre locations, and what they do is actually run a java process in the background and sysout all the system properties and pull the java version from that.  Java9 does not have the same system properties, and so there's really no way for me to get access or determine that it's actually java9. 

> Remove MaxPermSize from server scripts when Java 9 is used
> ----------------------------------------------------------
>
>                 Key: JBIDE-20292
>                 URL: https://issues.jboss.org/browse/JBIDE-20292
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>              Labels: Java9
>             Fix For: 4.3.x
>
>
> I'm not sure how easy this will be, but I think we need some way to do this.
> Right now when you set up your WildFly 9 to use JDK 9, it will not start because MaxPermSize is no longer allowed as an argument.
> The server will fail to start with this:
> {code}
> Unrecognized VM option 'MaxPermSize=256m'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> In JBIDE-19049 we concluded that for now the workaround is to remove that parameter from Launch config manually if needed. This still works, but it would be best if we could somehow detect which version of Java is to be used and adjust the script accordingly. I know it can be tricky, especially when you use an exec env with the server and not a specific JVM directly.
> One option would be to check for permgen support beforehand. But a problem I can see is that the exec env can change between server setup and server start, so we would need to check right before the start. Something like what they do here - via a script:
> https://answers.atlassian.com/questions/17903656/java-warning-ignoring-option-maxpermsize
> Maybe checking this at the time of server setup would still be better than nothing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)