I removed it even if it doesn't change the execution
Emmanuel
Francis De Brabandere a écrit :
> 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
>
|