continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis De Brabandere" <franci...@gmail.com>
Subject wrapper.java.maxmemory
Date Wed, 14 Nov 2007 14:30:09 GMT
just a question about wrapper.conf

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=3

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=384m

what is that 'm' doing after the 384? is that causing the default
value for maxmem? I think it should be removed, even if only for
clarity...
I got to that file because our builds seem to be interrupted without
any notice...

the wrapper.java.maxmemory doc:
The maximum amount of memory in megabytes that the JVM will be allowed to use.

the -Xmx java argument doc:
Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes.

I suppose this is a mix up somehow? Should I create a jira issue?

Regards

-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Mime
View raw message