[ https://issues.apache.org/jira/browse/KARAF-7071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308467#comment-17308467 ]
ASF subversion and git services commented on KARAF-7071: -------------------------------------------------------- Commit 328fb177a28f43cee0cc677d470cb54de4d6bbb9 in karaf's branch refs/heads/main from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=328fb17 ] Merge pull request #1337 from jbonofre/KARAF-7071 [KARAF-7071] Cleanup reference to *_MEM (replaced by JAVA_OPTS) > 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)