Re: [Wrapper-user] Problem with JVM parameters incase of JDK 5

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

Ashish,
The Wrapper expects that you break out the individual arguments
into their own properties. The way you are doing things will work
for Windows, but will fail if you use the wrapper.conf on UNIX
versions.

Do it like this:
wrapper.java.additional.1=-Xdebug
wrapper.java.additional.2=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
wrapper.java.additional.3=-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
wrapper.java.additional.4=-Djboss.platform.mbeanserver
wrapper.java.additional.5=-Dcom.sun.management.jmxremote
wrapper.java.initmemory=128
wrapper.java.maxmemory=256

When you say things are not being passed to the JVM correctly,
how do you know? What is the problem you are seeing?

You can see the generated java command line by setting the
following property:
wrapper.java.command.loglevel=INFO

Cheers,
Leif

Ashish Arya wrote:
> Hi All,
> I am using Java Service Wrapper to run JBoss as windows service. This
> was working fine on IBM and SUN JDK 1.4. but recently I shifted to SUN
> JDK 1.5 and noticed that the JVM arguments are not passed properly to
> the JRE. Below is the snippet of the wrapper conf file. I am using
> Java service wrapper version 3.2.3.
> wrapper.java.additional.1= -Xms128m -Xmx256m -Xdebug
> -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
> wrapper.java.additional.2=
> -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
> -Djboss.platform.mbeanserver -Dcom.sun.management.jmxremote
> even the spcified way of setting max and min heap size is also not working
> wrapper.java.initmemory=128
> wrapper.java.maxmemory=1024
> Please help me to understand, how to pass additional java parameters
> to wrapper API in case of JDK 5.
> Many thanks in advance.
> regards,
> Ashish