[Wrapper-user] Wrapper configuration problems

[Max S. <MSt...@li...>]

Leif,

 

   I wrote a code to dynamically modify wrapper.conf file in order to on the
fly change NT service's name, display name, and service description
parameters. When I analyzed this file, I though that this is a simple
properties file that you probably read and then apply internally. Because of
this, I thought that the order in which parameters appear in the file does
not matter. Apparently I thought wrong. In my file, parameters were in
different order then in your file, and when I tried to install the wrapper
and run my application as a service, it did not; the NT service did not
start. In order to trouble shoot the problem, I replaced my file with your
wrapper.conf file, tried to load and start the service again and it worked.
(Number of parameters in each file is the same). Therefore, I feel that for
some reason or not, the order in which parameters appear in your
wrapper.conf file is very important. Can you please let me know why did you
handle properties in such a way? Also, if this is not something you planned
for can you please update file that reads configuration properties, to first
read it and then apply them, so that the order in which they appear in the
Config file is not important. Thanks in advance.

 

 

Max