This repository was archived by the owner on Jan 7, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 7, 2024. It is now read-only.
[BUG] Wrong Java memory options in 169 release #168
Description
Activity
Parameter needs to be set without M now
MEM_LIMIT=1024M -> MEM_LIMIT=1024Reacted by Mickroz, condorXI, Marcus Wassén, AlTaiRius, b-col, Marco Pivetta, Jonathan Christison, eliotpeng, Corey Smith, Gilbert Sanchez and 5 moreReacted by Nicolas CoutinThis behaviour, and the documentation, was changed a year ago in #119 , the most recent update removed the compatibility shim in place to handle the transition.
If you update your environment variables as per the readme it will work.
Reacted by amiga23, Bryan, Mickroz, b-col and Jason Plum- pinned this issue
on Nov 30, 2022 Why this is closed? The same issue is still not fixed?
There is nothing to fix, you need to alter your deployment according to our documentation.
Ok, thanks, now I see the solution! Thnx!
Is there an existing issue for this?
Current Behavior
Invalid maximum heap size: -Xmx1024MM
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Expected Behavior
No response
Steps To Reproduce
Upgrade from 168 to 169
Environment
CPU architecture
arm64
Docker creation
Container logs
This message apears in a loop: Invalid maximum heap size: -Xmx1024MM Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.