Menu

#153 Cannot set wrapper.java.maxmemory larger 4096 MByte

v3.2.3
open-fixed
5
2017-04-14
2007-01-12
Anonymous
No

The 64 bit version on Linux and Solaris does not accept Heap-Size settings larger 4GB. When setting
wrapper.java.maxmemory=7000
wrapper.java.initmemory=7000
the following options for the Java process are used
-Xmx4096m -Xms4096m
instead of
-Xmx7000m -Xms7000m

Wrapper version: 3.2.3

Discussion

  • Leif Mortenson

    Leif Mortenson - 2007-01-12

    Logged In: YES
    user_id=228081
    Originator: NO

    Thanks for pointing this out. This has already been fixed and committed. It will be in the 3.2.4 release.

    For the time being, if you simply comment out your wrapper.java.maxmemory and wrapper.java.initmemory properties, then do the following, things should work for you.

    wrapper.java.additional.1=-Xmx7000m
    wrapper.java.additional.2=-Xms7000m

    Cheers,
    Leif

     
  • Leif Mortenson

    Leif Mortenson - 2007-01-12
    • milestone: --> v3.2.3
    • assigned_to: nobody --> mortenson
    • status: open --> open-fixed
     
  • Mateusz Matela

    Mateusz Matela - 2017-04-14

    if you simply comment out your wrapper.java.maxmemory and wrapper.java.initmemory

    Commenting out didn't work, wrapper still appended -Xmx4096m after the additional Xmx and it took precedence. What did work is setting wrapper.java.maxmemory to some invalid value, like aaa.

     

Log in to post a comment.