Menu
▾
▴
Re: [Wrapper-user] java application is failing to start on HP-UX
|
From: nehamunipalli MS <neh...@gm...> - 2009-09-18 06:33:30
|
Hi, I am not able to reproduce this problem as this is happening on one of the customer's system. To be able to understand where the SIGTERM is coming from i asked the customer to enable debugging and try starting the application again with the hope that I would be getting more information from the logs, as per your suggestion. However, I don't get any information from the logs. Am i missing out something? As per the mail enabling the debug mode should be giving the details of which process is sending the SIGTERM. I am not finding this information in the log. Thanks and Regards, Prasanna On 9/18/09, Tanuki Software Support <su...@ta...> wrote: > > Prasanna, > The SIGKILL that you saw in the log was sent by the Wrapper to > forcibly kill the the Java process after it did not shutdown within > the expected amount of time. The question is where the SIGTERM that > initiated the Wrapper to start its shutdown came from. > > Were you able to reproduce this problem? > > Sincerely, > Leif Mortenson > Tanuki Software, Ltd. > > On Fri, Sep 18, 2009 at 2:38 PM, nehamunipalli MS > <neh...@gm...> wrote: > > Hi, > > I did enable debugging for the wrapper. However, i am not getting any log > > messages about which process is sending the signal. From the previous > logs > > before enabling debug was enable there were log messages that there was a > > SIGKILL. This time after enabling debugging I am not seeing even that > > message. What I want to know if this is happening because the signal or > due > > to some other reason. Please let me know if there is any other way of > doing > > the investigation. > > > > This is happening on a HP-UX 11.11 host. > > > > Thanks, > > Prasanna > > > > > > On 9/7/09, Leif Mortenson <lei...@ta...> wrote: > >> > >> 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? > > -- > Leif Mortenson > Tanuki Software, Ltd. > 6-16-7-1001 Nishi-Kasai, Edogawa-ku > Tokyo 134-0088 Japan > Tel/Fax: +81-3-3878-3211 > http://www.tanukisoftware.com > lei...@ta... > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
