|
From: Leif M. <le...@ta...> - 2005-12-12 04:08:40
|
Donatas,
Could you try this with wrapper.debug=true set? That way you will
be able to see whether
the shutdown is being started or not.
How is your program being started? Is it set up in the /etc/init.d
directory? Have you set
up the appropriate symbolic links to start and stop the daemon at the
various run levels?
If the shutdown sym link is not there then the system will just kill the
process on shutdown
as a last resort. That may be what you are seeing.
This page is for Debian, but take a look at this:
http://wrapper.tanukisoftware.org/doc/english/launch-nix-boot-debian.html
Cheers,
Leif
Donatas Ciuksys wrote:
> Hi,
>
> I'm using Wrapper 3.1.2 on Fedora core 4 linux. The problem occurs during
> restart of linux machine (with command reboot). This is wrapper.log:
>
> STATUS | wrapper | 2005/12/07 17:22:41 | --> Wrapper Started as Daemon
> STATUS | wrapper | 2005/12/07 17:22:41 | Launching a JVM...
> INFO | jvm 1 | 2005/12/07 17:22:56 | Wrapper (Version 3.1.2)
> http://wrapper.tanukisoftware.org
> INFO | jvm 1 | 2005/12/07 17:22:56 |
> STATUS | wrapper | 2005/12/07 17:25:10 | TERM trapped. Shutting down.
> STATUS | wrapper | 2005/12/07 17:26:47 | --> Wrapper Started as Daemon
> STATUS | wrapper | 2005/12/07 17:26:48 | Launching a JVM...
> INFO | jvm 1 | 2005/12/07 17:27:03 | Wrapper (Version 3.1.2)
> http://wrapper.tanukisoftware.org
>
> >From my application log file I see that method stop() was not called during
> shutdown. I suppose this is Linux issue - possibly too litle time is given
> for Wrapper to terminate?
>
> Greetings,
> Donatas
|