Re: [Wrapper-user] 4096MB heap limit

[Leif M. <le...@ta...>]

Tom,
The 4Gb limit is very historical. It went in long before 64 bit machines
were in the picture. This limit has been removed from the source for
the 3.3.0 release. (which is pending)

As mentioned, in 3.2.3, you cam work around this easily by doing the
following:
wrapper.java.additional.5=-Xms6000m
wrapper.java.additional.6=-Xmx6000m
wrapper.java.initmemory=0
wrapper.java.maxmemory=0

Setting the Wrapper's memory limits to 0 makes it possible to specify
them manually:
http://wrapper.tanukisoftware.org/doc/english/prop-java-maxmemory.html
http://wrapper.tanukisoftware.org/doc/english/prop-java-initmemory.html

Also set the following. It will let you see the generated java command
to verify that it is generating what you expect.
wrapper.java.command.loglevel=INFO

Cheers,
Leif

Chandra Patni wrote:
>
> Wrapper-3.2.3 64 bit for linux
>
> Make sure that you have not specified wrapper.java.initmemory and 
> wrapper.java.maxmemory.
>
> BTW, you’ve not specified the units of memory and the default unit is 
> byte.
>
> http://java.sun.com/j2se/1.5.0/docs/tooldocs/solaris/java.html
>
> ------------------------------------------------------------------------
>
> *From:* wra...@li... 
> [mailto:wra...@li...] *On Behalf Of *Tom 
> Saulpaugh
> *Sent:* Wednesday, September 26, 2007 10:52 AM
> *To:* wra...@li...
> *Subject:* Re: [Wrapper-user] 4096MB heap limit
>
> I did:
>
> wrapper.java.additional.13=-Xms6000
>
> wrapper.java.additional.14=-Xmx6000
>
> and it still pegs the heap at 4096.
>
> Are you using the most current version? If not, which version are you 
> using?
>
> Thanks,
>
> Tom
>
> ------------------------------------------------------------------------
>
> *From:* wra...@li... 
> [mailto:wra...@li...] *On Behalf Of 
> *Chandra Patni
> *Sent:* Wednesday, September 26, 2007 10:18 AM
> *To:* wra...@li...
> *Subject:* Re: [Wrapper-user] 4096MB heap limit
>
> I have also highlighted this issue before. The workaround is to use
>
> java.additional.N=-Xmx…
>
> Don’t use built-in parameters in wrapper.
>
> ------------------------------------------------------------------------
>
> *From:* wra...@li... 
> [mailto:wra...@li...] *On Behalf Of *Tom 
> Saulpaugh
> *Sent:* Wednesday, September 26, 2007 9:39 AM
> *To:* wra...@li...
> *Subject:* [Wrapper-user] 4096MB heap limit
>
> In my previous post I was referring to this code block within wrapper.c
>
> /* Maximum JVM memory */
>
> maxMemory = getIntProperty(properties, "wrapper.java.maxmemory", 0);
>
> if (maxMemory > 0) {
>
> maxMemory = __min(__max(maxMemory, initMemory), 4096); /* initMemory 
> <= n <= 4096 */
>
> if (strings) {
>
> strings[index] = malloc(sizeof(char) * (5 + 4 + 1)); /* Allow up to 4 
> digits. */
>
> sprintf(strings[index], "-Xmx%dm", maxMemory);
>
> }
>
> index++;
>
> }
>
> In the most recent wrapper.c the code has been changed to:
>
> /* Maximum JVM memory */
>
> maxMemory = getIntProperty(properties, "wrapper.java.maxmemory", 0);
>
> if (maxMemory > 0) {
>
> maxMemory = __max(maxMemory, initMemory); /* initMemory <= n */
>
> if (strings) {
>
> strings[index] = malloc(sizeof(char) * (5 + 4 + 1)); /* Allow up to 4 
> digits. */
>
> if (!strings[index]) {
>
> outOfMemory("WBJCAI", 9);
>
> return -1;
>
> }
>
> sprintf(strings[index], "-Xmx%dm", maxMemory);
>
> }
>
> index++;
>
> }
>
> which doesn't set a 4096MB limit. Is there any other code setting a limit?
>
> Has anyone created a >4GB heap?
>
> Thanks,
>
> Tom
>