|
From: Ashish A. <ash...@ya...> - 2007-07-13 06:17:41
|
Hi Leif, Thanks a lot for your reply. After passing JVM parameters individually, as suggested by you, I noticed that they are passed properly to JVM. I have confirmed this using jconsole utility. But still my problem is not resolved. When I run JBoss using run.bat file, for one of the operations in my application, the memory usage goes above 500 MB, which is very well expected. But when I run the JBoss using Wrapper and passing JVM parameters through conf file, the memory hangs around 190 MB and the same operation takes longer time to finish. That also mean that performance of my appliction drops when I use wrapper to run JBoss against run.bat file. I am unable to understand this behavior. Please help me. regards, Ashish ----- Original Message ---- From: Leif Mortenson <le...@ta...> To: wra...@li... Sent: Wednesday, July 11, 2007 3:47:53 PM Subject: Re: [Wrapper-user] Problem with JVM parameters incase of JDK 5 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 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user ____________________________________________________________________________________ Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/ |