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

[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.