Re: [Wrapper-user] Additional parameters to Java Service Wrapper

[Francesco S. <f.s...@ci...>]

Hi Lief.
I try to explain my situation.

I have an amount of j2ee instance configured with JSW: java parameters 
and application parameters are defined into JSW (one wrapper.conf file).

Some parameters, however, are specifics for instance and it's possible 
that not all instances needs for additional parameters.

For example, suppose that in production environment just a single 
instance has an of out of memory problem (is just an example). In this 
situation I would like to "debug" my instance, so I need to specify a 
debug port just for this instance.

In this example I need to define a property just for an instance and 
just for a _limited time_.

If I am able to add multiple parameters with one property, I can specify 
this property always and use it when I need it (look at the example 
explained in first email).

In this case, additional parameters are defined into an external file (a 
configuration file for instance) and not into wrapper.conf file. The 
latter one contains just the property 
"wrapper.java.additional.XX=%ADDITIONAL%".

Your suggestion to use an "include" file is a good solution (thanks 
again) but for me is too hard to manage than a single parameter. For 
example, I don't know how many parameters I might need.

Moreover, in a (semi) automated infrastructure is difficult to define 
how many discontinious "X" values to use for any instance.

What do you think about?
I hope this scenario is more or less clear.

Thanks a lot.
Francesco.




Il 26/08/2011 16:59, Leif Mortenson ha scritto:
> Francesco,
> The way the properties are broken up is currently by design to give
> you the most control over them.  We don't have any plans to change
> that at the moment, but we are always open to ways to improve the
> Wrapper.  If you could describe what you are trying to do, we can
> consider a solution or suggest a way of doing it using the current
> functionality.
>
> Cheers,
> Leif
>