You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by spacemonkey iv <sp...@gmail.com> on 2011/05/22 04:30:41 UTC

Re: Clarification on --JvmXX windows service installer parameters

+user@commons.apache.org

Thanks for pointing me to the procrun documentation and the commons-users
mailing lists. I'll include both mailing lists on this question.

I'm still not clear after looking at the documentation for procrun about
what's the difference in setting the Java memory options with --JvmOptions
vs. --JvmXX.

The relevant text that I have found so far says this:

*++JvmOptions - List of options in the form of -D or -X that will be passed
to the JVM. The options are separated using either # or ; characters. if you
need to embed either # or ; character put them inside single quotes. (Not
used in exe mode.)*
*
*
*--JvmMs - Initial memory pool size in MB. (Not used in exe mode.)*
*
*
*--JvmMx - Maximum memory pool size in MB. (Not used in exe mode.)*
*
*
*--JvmSs - Thread stack size in KB. (Not used in exe mode.)*


I'm still unclear. If it turns out that I still need to use
--JvmOptions=-Xmx=2048, then should I continue using --JvmMx=2048? What's
the difference between these two techniques? Do the --JvmXX options need to
be equal or greater than the values set with --JvmOptions?

Thanks

On Sat, May 21, 2011 at 6:43 PM, sebb <se...@gmail.com> wrote:

> On 21 May 2011 01:52, space monkey <sp...@gmail.com> wrote:
> > Tomcat 7.0.14
> > Windows XP+
> >
> > Hello Tomcat users,
> >
> > I am trying to understand how the *--JvmMs*, *--JvmMx*, and *JvmSs*
> windows
> > service install paramerters differ from setting the JVM memory values
> > explicitly with *--JvmOptions*?
> >
> > Please see this forum post that described my initial problem:
> >
> http://www.coderanch.com/t/537921/Tomcat/Issues-multiple-Tomcat-services-Windows
> > .
> >
> > Basically, I discovered that I needed to try something like* tomcat7.exe
> > //US/t1 --JvmOptions=-Xmx=2048* after finding out that *--JvmMx=2048* did
> > not get me the desired results.
> >
> > How do the --JvmXX flags work exactly and if I am setting memory values
> with
> > JvmOptions, should I still bother setting anything with the --JvmXX?
> >
> > Thanks!
>
> This looks to be a question on Commons Daemon Procrun, which is documented
> here:
>
> http://commons.apache.org/daemon/procrun.html
>
> Questions about Commons Daemon ideally belong on the Commons User list.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>