|
From: Leif M. <le...@ta...> - 2007-06-28 02:03:38
|
Andrew,
I am not exactly clear as to where your java class will be running.
The -X JVM options need to be set before the JVM is launched by the
Wrapper.
What kinds of situations will you be doing this? Is it only for
development or do you need this for run time?
Basically, I would use a cascading configuration file to do this.
That way you could completely rewrite that file each time without
worrying about the contents of your main wrapper.conf file.
http://wrapper.tanukisoftware.org/doc/english/props-cascading.html
The Java command line is created in the wrapper.c source file of
the Wrapper. Discuss any changes with me before you make them
as it may make sense to change my source as well.
Cheers,
Leif
Andrew Perepelytsya wrote:
> Hi guys,
>
> We are trying to embed a profiler agent in the application launched
> with the
> wrapper. The -X JVM option value depends on the JDK version used. To
> better
> get the idea, have a look at
> http://mule.mulesource.org/display/MULE/Profiling+Mule+with+YourKit
>
> So, I can manually edit the wrapper.conf and set the params. The idea
> is to
> automate the process and put this logic in a Java class that would modify
> the launch parameters for the main JVM. So far, I found no straightforward
> way to do it. Is it possible? Could you please point to the location a
> child
> JVM options are constructed?
>
> Thanks in advance,
> Andrew
|