[
https://issues.apache.org/jira/browse/IGNITE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091750#comment-15091750
]
Denis Magda commented on IGNITE-255:
------------------------------------
Saikat,
I'm quite sure that the proposed solution won't work for the versions that
contain dashes or underscore (like, 1.3.1-beta or 1.3.1_05). However such
versions strings are possible according to [1]
Probably we can leverage regexp there somehow. What do you think? The regexp
can just take a major version.
Also we must be sure that the scripts will work not only on Oracle JDK but on
others as well: at least on OpenJdk, IBM JDK.
If it won't be possible to calc the version properly for all the cases I would
omit setting MaxPermSize/MaxMetaspaceSize at all.
[1] http://www.oracle.com/technetwork/java/javase/versioning-naming-139433.html
> Jvm8 warns that MaxPermSize is ignored
> --------------------------------------
>
> Key: IGNITE-255
> URL: https://issues.apache.org/jira/browse/IGNITE-255
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: sprint-1
> Reporter: Sergey Kozlov
> Assignee: Saikat Maitra
>
> Jaba8 doesn't support MaxPermSize anymore. Either we should replace it in
> ignite.sh by a similar option of Java8 or set it only if ignite.sh started
> for Java7
> {noformat}
> D:\GridGain\Ignite-SP1\ignite-fabric-1.0.0-RC1-SNAPSHOT>bin\ignite.bat
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> [15:50:16] __________ ________________
> [15:50:16] / _/ ___/ |/ / _/_ __/ __/
> [15:50:16] _/ // (_ / // / / / / _/
> [15:50:16] /___/\___/_/|_/___/ /_/ /___/
> [15:50:16]
> [15:50:16] ver. 1.0.0-RC1-SNAPSHOT#20150214-sha1:4d01989c
> [15:50:16] 2015 Copyright(C) Apache Software Foundation
> [15:50:16]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
