Re: [Wrapper-user] Java Service Wrapper 3.3.8 released

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

Hi all,
We had an issue reported against 3.3.8 today that is a non issue
unless you use wrapper.working.dir, then it is fairly critical.
On UNIX platforms when running with the wrapper.daemonize property,
the Wrapper will get confused about its working directly and not be
able to load in any include files from the wrapper.conf file that are
defined relative to the wrapper binary.

The work around is to either move everything into the wrapper.conf and
not use include files, or to simply add another include relative to
both the wrapper binary and to the location of the
wrapper.working.dir.

For example:
---
#include ../conf/wrapper-settings.conf
wrapper.working.dir=../
wrapper.logfile = logs/wrapper.log
---
Should become:
---
#include ../conf/wrapper-settings.conf
#include conf/wrapper-settings.conf
wrapper.working.dir=../
wrapper.logfile = logs/wrapper.log
---
This works because the Wrapper will load the wrapper-settings.conf
file when the current directory is in the bin directory the first
time, then it will reload the configuration and read the second
include after changing to the parent directory.

We have already fixed this for a 3.3.9 release and will try to get it
out shortly.

Sorry for the inconvenience.

Sincerely,
Leif Mortenson
Tanuki Software, Ltd.

On Sat, Nov 7, 2009 at 5:42 AM, Leif Mortenson
<lei...@ta...> wrote:
> Hi all,
> We are proud to announce the release of version 3.3.8 of the Java
> Service Wrapper.
> http://wrapper.tanukisoftware.org/doc/english/download.jsp
>
> We released this version so quickly to fix a problem in 3.3.7 UNIX
> versions which
> prevented a copy of the Wrapper which was started as a daemon process from
> being stopped with the Wrapper's shell script.
>
> We also had been working on some changes to the way log files are rotated and
> purged.  The new system should be much more flexible, while remaining compatible
> with past configuration files.
>
> The ordering of jar files resulting from a wildcard classpath property are now
> sorted to ensure consistent operation when there are duplicate classes
> or resources.
>
> There were also a few other bug fixed and enhancements made.  Please review
> the release notes for a full list of changes.
> http://wrapper.tanukisoftware.org/doc/english/release-notes.html
>
> We recommend that all users of 3.3.7 upgrade to 3.3.8 due to the UNIX problem.
>
> Please let me know if you have any questions about the release.
>
> Sincerely,
> Leif Mortenson
> Tanuki Software, Ltd.