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

Posted to issues@fineract.apache.org by "Aleksandar Vidakovic (Jira)" <ji...@apache.org> on 2024/01/06 15:04:00 UTC

[jira] [Resolved] (FINERACT-2012) Fineract resource settings

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

Aleksandar Vidakovic resolved FINERACT-2012.
--------------------------------------------
    Resolution: Fixed

> Fineract resource settings
> --------------------------
>
>                 Key: FINERACT-2012
>                 URL: https://issues.apache.org/jira/browse/FINERACT-2012
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Deployment
>            Reporter: Peter Santa
>            Assignee: Aleksandar Vidakovic
>            Priority: Major
>              Labels: BeanSalad
>             Fix For: 1.9.0
>
>
> Currently the build.gradle file for fineract-provider sets some options for the Java runtime. Among these there are some memory-related options:
>             '-Xms1G',
>             '-XX:MinRAMPercentage=25',
>             '-XX:MaxRAMPercentage=80',
> Unfortunately these options can't be easily overwritten via environment variables, because:
> _JAVA_OPTIONS --> this is a non-standard option, not all JVM implementations necessarily support this (https://bugs.openjdk.org/browse/JDK-4971166), and instead of _JAVA_OPTIONS, JAVA_TOOL_OPTIONS is recommended
> JAVA_TOOL_OPTIONS --> unfrtunately explicitly specified command line arguments take precedence of values set as part of JAVA_TOOL_OPTIONS, so this method doesn't work
> JDK_TOOL_OPTIONS --> same issue as with JAVA_TOOL_OPTIONS
> The best way to approach this would be to not set these memory-related options (at least not the maximums) during build-time, enabling the usage of JAVA_TOOL_OPTIONS/JDK_TOOL_OPTIONS.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)