You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/03/25 05:07:00 UTC
[jira] [Commented] (KARAF-7071) KARAF-6887 Dropped support for
JAVA_MAX_MEM
[ https://issues.apache.org/jira/browse/KARAF-7071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308386#comment-17308386 ]
ASF GitHub Bot commented on KARAF-7071:
---------------------------------------
jbonofre opened a new pull request #1337:
URL: https://github.com/apache/karaf/pull/1337
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> KARAF-6887 Dropped support for JAVA_MAX_MEM
> -------------------------------------------
>
> Key: KARAF-7071
> URL: https://issues.apache.org/jira/browse/KARAF-7071
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.3.0
> Reporter: Duncan Grant
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
>
> The bin/setenv script still lists JAVA_MAX_MEM for increasing the java max memory but this was dropped from bin/inc here in this PR [https://github.com/apache/karaf/pull/1226]
> It is still supported by karaf.bat, there's no similar code path in bin/karaf, so I assume that the intention is for this to still be supported.
> I'm happy to create a PR for this but would like to clarify first:
> * should this still be supported or should all opt be via JAVA_NON_DEBUG_OPTS
> * if yes should this be supported by bin/karaf
> * should JAVA_MIN_MEM, JAVA_PERM_MEM, JAVA_MAX_PERM_MEM also be supported? I guess so as I think karaf still supports jdk 1.7 and I think these were only removed as jvm options in jdk1.8
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)