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

[Markus S. <sc...@gm...>]

HI
I only used the init-/maxmemory options, and never tested the other ones.
Maybe they even work, but sergio did not comment them out in his
wrapper.conf?

Markus

2008/1/22, Nathan Wray <wr...@de...>:
>
>
> 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 -Xmsparameter 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...> 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...>:
> > >
> > >
> > > 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...
> > >
> > >
> > > --
> > > View this message in context:
> > > http://www.nabble.com/Wrapping-JBoss%3A-Problems-with-memory-definition-tp14952013p14952013.html
> > > Sent from the Java Service Wrapper mailing list archive at Nabble.com.
> > >
> > >
> > > -------------------------------------------------------------------------
> > >
> > > This SF.net email is sponsored by: Microsoft
> > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > _______________________________________________
> > > Wrapper-user mailing list
> > > Wra...@li...
> > > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> > >
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
> >
>
>
> --
> Nathan Wray
> nw...@de...
> --
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>