Re: [Wrapper-user] Wrapping JBoss: Problems with memory definition

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

Nathan,
Those memory properties have been around since the first versions
of the Wrapper.  They do nothing other than add the -Xmx and -Xms
arguments to the JVM when it is launched.  If you comment them out
you can safely define them yourself.

If they are both there however then you will get the memory
arguments twice.

If you want to verify the generated command line, do one of the
following:
wrapper.debug=true
wrapper.java.command.loglevel=INFO

Cheers,
Leif

Nathan Wray wrote:
>
> Hi Markus;
>
> Reading the documentation for the initmemory / maxmemory properties 
> says that they're optional, that they can be commented out and the 
> user can use the -Xmx/-Xms flags in the "additional" properties. 
>
> What are the implications or side effects of not using initmemory / 
> maxmemory, and instead setting the memory values manually?  The 
> scenario Sergio is describing seems to be valid per the docs.
>
> "If this property is set to 0 then it is also possible to specify the 
> -Xms parameter manually using the wrapper.java.additional.<n> 
> <http://wrapper.tanukisoftware.org/doc/english/prop-java-additional-n.html>property."
>
> Thanks
> Nathan
>
>
> On 1/18/08, * Markus Schlegel* <sc...@gm... 
> <mailto:sc...@gm...>> wrote:
>
>     Hi
>
>     Wrapper has two distinct properties for this:
>
>     # Initial Java Heap Size (in MB)
>     wrapper.java.initmemory=8
>
>     # Maximum Java Heap Size (in MB)
>     wrapper.java.maxmemory=768
>
>     regards,
>     Markus Schlegel
>
>     2008/1/18, serdsch <ser...@ev...
>     <mailto:ser...@ev...>>:
>
>
>         Hi,
>
>         I want to run JBoss as a Windows Service to avoid problems
>         with starting the
>         server from CruiseControl. I use the JavaServiceWrapper and
>         wrote a
>         wrapper.conf file with all necessary parameters to run JBoss
>         suited for my
>         test system. When I start JBoss with the batch script we used
>         before,
>         everything works just fine. When I start it with the wrapper
>         the startup is
>         much slower until it stops executing, throwing a heap space
>         exception.
>
>         This is how I define the memory allocation in the batch script:
>
>         set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m
>
>         I get exactly the same problems and exception starting JBoss
>         when I comment
>         this allocation, so I guess for some reason the
>         JavaServiceWrapper can't get
>         the memory allocation right. This is how I define it in
>         wrapper.conf:
>
>         rem JVM memory allocation pool parameters. Modify as appropriate.
>         wrapper.java.additional.6=-Xms128m
>         wrapper.java.additional.7=-Xmx512m
>
>         Does any of you have an idea? What am I missing?
>         Any help is highly appreciated...
>