[Wrapper-user] wrapper.daemonize: signal trap problem

[John Q. <jqu...@jq...>]

Hey Folks:

I'm having some difficulty debugging a problem I'm seeing when daemonizing my application with the wrapper.  I'm hoping that someone more knowledgeable in these things may be able to point me in the right direction, or bring any errors of mine to light.  Thanks in advance for your consideration.  Here are the details.

I've implemented a 'Daemonizer' class that my Application must extend:

 http://pastebin.com/m54ac98cd

Here's a test class:

 http://pastebin.com/m520ea3e4

On a 'CentOS release 5 (Final)' machine, when I run the DaemonizerTest:

 "$WRAPPER_CMD" "$WRAPPER_CONF" wrapper.syslog.ident=$APP_NAME wrapper.pidfile="$PIDFILE"

 (this is actually run using the wrapper init.d script specifying the 'console' run mode)

Everything works correctly, and when I send a SIGINT via the keyboard, or a SIGTERM via kill(1), the Daemonizer.shutdown() hook is properly called.  However, when I run the application as a daemon, such as:

 "$WRAPPER_CMD" "$WRAPPER_CONF" wrapper.syslog.ident=$APP_NAME wrapper.pidfile="$PIDFILE" wrapper.daemonize=TRUE

 (this is actually run using the wrapper init.d script specifying the 'start' run mode)

And subsequently send a SIGTERM via kill(1), the shutdown() method is not called.  I've tried various things to debug this, but am still left scratching my head.

What am I doing wrong?

Thanks so much.

- John Quigley