[BUG] Wrong Java memory options in 169 release

[amiga23]

Is there an existing issue for this?

• I have searched the existing issues

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

- OS: manjaro/archlinux ARM64
- How docker service was installed:
k3s

CPU architecture

arm64

Docker creation

Kubernetes deployment

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.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

[amiga23]

Parameter needs to be set without M now
MEM_LIMIT=1024M -> MEM_LIMIT=1024

[thespad]

This 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.

[ints99]

Why this is closed? The same issue is still not fixed?

[Roxedus]

There is nothing to fix, you need to alter your deployment according to our documentation.

[ints99]

Ok, thanks, now I see the solution! Thnx!