Re: [Wrapper-user] why #include-file is not reloaded

[Leif M. <le...@ta...>]

Markus,
    I tested this out a little bit.   Properties in include files are 
correctly being reloaded
That is not your problem.  It is actually with the working dir.

    The problem is that the Wrapper loads the configuration files the 
first time when its
working directory is the location of the wrapper.exe.  As stated in the 
docs, once the
configuration file is fully loaded, the working directory will be 
changed as per the
value specified with wrapper.working.dir.
    This means that the first time around, your include file reference 
is correct.
However, when it attempts to go back and reload the config file later, 
this relative
reverence is no longer valid your include file is being looked for at
../../startup.conf relative to the wrapper.exe

    I view this as a bug in the wrapper that I'll fix for the next 
release at the end of the
month.  For now, you can work around this by using the following two include
references.  This works because the wrapper ignores include files that 
do not exist.

#include ../startup.conf
#include startup.conf

Cheers,
Leif

Markus Müller wrote:
> Hi together,
> my wrapper.conf contains following lines:
>
> wrapper.java.mainclass=myclass1
> wrapper.working.dir=../
> #include ../startup.conf
> wrapper.restart.reload_configuration=TRUE
>
> startup.conf conatins only one line:
>
> wrapper.java.mainclass=myclass2
>
> If i start wrapper, myclass2 will start perfectly. But if i do WrapperManager.restart(); in my code, myclass1 starts up. I did various test and I think, while reolading the configuration, #include-files are not used. Any idea, why not?
> I'm using wrapper Version 3.2.3. myclass1 and myclass2 implements WrapperListener.
>
>