Menu
▾
▴
Re: [Wrapper-user] Wrapping JBoss: Problems with memory definition
|
From: Mantrao, N. <nm1...@nc...> - 2008-01-23 06:21:30
|
Hi, =20 Could anyone tell me how to "un-subscribe" from this mailing list. I have tried a couple of times, but all in vein.=20 Any help will be highly appreciated. =20 Thanks, Nikhil Mantrao. ________________________________ From: wra...@li... [mailto:wra...@li...] On Behalf Of Nathan Wray Sent: Wednesday, January 23, 2008 12:03 AM To: wra...@li... Subject: Re: [Wrapper-user] Wrapping JBoss: Problems with memory definition 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. =20 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.ht ml> property." Thanks Nathan On 1/18/08, Markus Schlegel <sc...@gm...> wrote:=20 Hi =09 Wrapper has two distinct properties for this: =09 # Initial Java Heap Size (in MB) wrapper.java.initmemory=3D8 =09 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=3D768 =09 regards, Markus Schlegel=20 =09 =09 2008/1/18, serdsch <ser...@ev...>:=20 =09 Hi, =09 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=20 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.=20 =09 This is how I define the memory allocation in the batch script: =09 set JAVA_OPTS=3D%JAVA_OPTS% -Xms128m -Xmx512m =09 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=20 the memory allocation right. This is how I define it in wrapper.conf: =09 rem JVM memory allocation pool parameters. Modify as appropriate. wrapper.java.additional.6=3D-Xms128m wrapper.java.additional.7=3D-Xmx512m=20 =09 Does any of you have an idea? What am I missing? Any help is highly appreciated... =09 =09 -- 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. =09 =09 =09 ------------------------------------------------------------------------ -=20 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/=20 _______________________________________________ Wrapper-user mailing list Wra...@li...=20 =09 https://lists.sourceforge.net/lists/listinfo/wrapper-user =09 =09 ------------------------------------------------------------------------ - 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=20 =09 =09 --=20 Nathan Wray nw...@de... --=20 |
