Re: [Wrapper-user] java application is failing to start on HP-UX

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

Nehamuni,
The Wrapper and JVM appeared to have been working normally since
August 27th.   The application shutdown was triggered by the Wrapper
receiving a SIGTERM.

This can happen if someone runs the wrapper script with the "stop"
command, or if another process issued a SIGTERM.

It is possible to see where the SIGTERM came from if you set the
wrapper.debug=true property and then reproduce it.

You can also tell the Wrapper to completely ignore SIGTERM signals
using the following property:
http://wrapper.tanukisoftware.org/doc/english/prop-ignore-signals.html

I had a customer several years ago running Solaris and another process
had a bug that was sending out SIGTERMS to the wrong processes.  This
was sometimes causing the Wrapper to shutdown.  The above property
will tell the Wrapper to ignore such signals.

There is no way to get additional log information without reproducing the event.

Sincerely,
Leif Mortenson
Tanuki Software, Ltd.

On Mon, Sep 7, 2009 at 8:23 PM, nehamunipalli MS<neh...@gm...> wrote:
> Hi Chirstian,
>  I am not sure about this issue as this is happening at a customer site. Are
> there other steps that I can follow to get more information on what is
> happening like getting more logs about the problem?
>
>
> On 9/7/09, Christian Mueller <chr...@ta...> wrote:
>>
>> Hi,
>>
>> you installed the daemon on august 27th and the next time the daemon
>> received a SIGTERM on September 3rd.
>> did your daemon run for 6.5 days fine and suddenly terminate?
>> In the log, the wrapper seems to behave normal. The wrapper process
>> received a SIGTERM and therefore tries to shutdown the java process. as the
>> jvm didn't finish after a 5sec timeout the wrapper terminates it with a
>> SIGKILL signal.
>> Do you have an idea what could the SIGTERM have caused?
>>
>> Sincerely,
>> Christian Mueller
>> Tanuki Software, Ltd.
>>
>>
>> On Mon, Sep 7, 2009 at 4:00 PM, nehamunipalli MS <neh...@gm...>
>> wrote:
>>>
>>> Our java application is failing to start. Following are the messages
>>> getting logged.
>>>
>>> STATUS | wrapper | 2009/08/27 12:06:38 | --> Wrapper Started as Daemon
>>> STATUS | wrapper | 2009/08/27 12:06:38 | Launching a JVM...
>>> INFO | jvm 1 | 2009/08/27 12:06:40 | java version "1.5.0.06"
>>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java(TM) 2 Runtime Environment,
>>> Standard Edition (build 1.5.0.06-_12_jan_2007_03_27)
>>> INFO | jvm 1 | 2009/08/27 12:06:40 | Java HotSpot?(TM) Server VM (build
>>> 1.5.0.06 jinteg:01.12.07-02:33 PA2.0 (aCC_AP), mixed mode)
>>> INFO | jvm 1 | 2009/08/27 12:06:40 |
>>> INFO | jvm 1 | 2009/08/27 12:06:41 | Wrapper (Version 3.2.3)
>>> http://wrapper.tanukisoftware.org
>>> INFO | jvm 1 | 2009/08/27 12:06:41 | Copyright 1999-2006 Tanuki Software,
>>> Inc. All Rights Reserved.
>>> INFO | jvm 1 | 2009/08/27 12:06:41 |
>>> STATUS | wrapper | 2009/09/03 17:37:26 | TERM trapped. Shutting down.
>>> WARN | wrapper | 2009/09/03 17:38:31 | JVM exited unexpectedly while
>>> stopping the application.
>>> STATUS | wrapper | 2009/09/03 17:38:31 | JVM exited in response to signal
>>> SIGKILL (9).
>>>
>>> Please let me know what the problem is and how this can be resolved? Is
>>> this a known issue?