Menu
▾
▴
Re: [Wrapper-user] Wrapper shuts down on Linux
|
From: David H. <dho...@gm...> - 2008-09-05 01:55:01
|
It looks like I am already using 3.3.1. I have set wrapper.ping.timeout=60 but I have not set wrapper.startup.timeout. What do you recommend I set this to? Regarding the Linux server, I do suspect that it gets heavy CPU usage at times. -Dave On Thu, Sep 4, 2008 at 5:50 PM, Leif Mortenson <le...@ta...>wrote: > David, > What version of the Wrapper are you running? There was a bug in > 3.3.0 where the JVM process was not always being killed correctly if > it was found to be frozen. That might explain why the JVM was not > restarting. You should try upgrading to 3.3.1 and see if that > resolves the problem for you. > http://wrapper.tanukisoftware.org/doc/english/release-notes.html > > Lengthening the wrapper.ping.timeout and wrapper.startup.timeout s > would help if the problem is indeed CPU related. > > Cheers, > Leif > > On Fri, Sep 5, 2008 at 8:19 AM, David Hoffer <dho...@gm...> wrote: > > Leif, > > > > I have made the debug change to the conf file. Previously I had bumped > up > > the timeout to 60 seconds so who knows it may not happen again. > > > > Ideally, since I have seen this happen twice now, is that I would like an > > auto retry/restart feature so that it will continually try to restart if > for > > whatever reason it shuts down. Is this possible on Linux? > > > > -Dave > > > > On Thu, Sep 4, 2008 at 10:00 AM, Leif Mortenson <le...@ta... > > > > wrote: > >> > >> David, > >> Assuming that the Wrapper has been working correctly for a few days as > >> you say, I am unsure as to what is happening here with just the > >> information you provided. > >> Could you please set the wrapper.debug=true property and reproduce > >> this? Then send me the resulting full wrapper.log file to my email > >> directly as it is large for the list. > >> > >> >From the log, the JVM appears to have frozen and was killed for some > >> reason. When the Wrapper then attempts to relaunch the JVM process, > >> it fails to start within 30 seconds. > >> > >> What is the status of your system when this happens? Is it possible > >> that the system is being bogged down by another process? If the JVM > >> is failing to receive any CPU for a long period of time, it could > >> appear to be frozen. That would also explain why it would take a long > >> time for the next JVM invocation to start up. In either case, there > >> are timeouts which can be extended to avoid this problem. > >> > >> Cheers, > >> Leif > >> > >> On Thu, Sep 4, 2008 at 11:47 AM, David Hoffer <dho...@gm...> > wrote: > >> > I am using the wrapper on Linux running as a daemon. For some reason > >> > after > >> > running for a while (few days) it shuts down. Here is the log: > >> > > >> > INFO | jvm 1 | 2008/08/31 15:22:52 | > >> > -------------------------------------- > >> > ERROR | wrapper | 2008/09/02 07:49:32 | JVM appears hung: Timed out > >> > waiting for signal from JVM. > >> > ERROR | wrapper | 2008/09/02 07:49:33 | JVM did not exit on request, > >> > terminated > >> > STATUS | wrapper | 2008/09/02 07:49:40 | Launching a JVM... > >> > ERROR | wrapper | 2008/09/02 07:50:10 | Startup failed: Timed out > >> > waiting > >> > for a signal from the JVM. > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > > ------------------------------------------------------------------------ > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Advice: > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | The Wrapper consists of a > >> > native > >> > component as well as a set of classes > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | which run within the JVM > that > >> > it > >> > launches. The Java component of the > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper must be initialized > >> > promptly after the JVM is launched or the > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper will timeout, as > just > >> > happened. Most likely the main class > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | specified in the Wrapper > >> > configuration file is not correctly initializing > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | the Wrapper classes: > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > com.dhs.service.JavaServiceWrapperWebServiceLauncher > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | While it is possible to do > so > >> > manually, the Wrapper ships with helper > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | classes to make this > >> > initialization processes automatic. > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Please review the > integration > >> > section of the Wrapper's documentation > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | for the various methods > which > >> > can > >> > be employed to launch an application > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | within the Wrapper: > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > http://wrapper.tanukisoftware.org/doc/english/integrate.html > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > > ------------------------------------------------------------------------ > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > ERROR | wrapper | 2008/09/02 07:50:11 | JVM did not exit on request, > >> > terminated > >> > STATUS | wrapper | 2008/09/02 07:50:11 | JVM received a signal > SIGKILL > >> > (9). > >> > STATUS | wrapper | 2008/09/02 07:50:16 | Launching a JVM... > >> > ERROR | wrapper | 2008/09/02 07:50:46 | Startup failed: Timed out > >> > waiting > >> > for a signal from the JVM. > >> > ADVICE | wrapper | 2008/09/02 07:50:46 | > >> > > >> > What may be causing this? I am not a Linux guur. I have used the > >> > wrapper > >> > on Windows with no issues. My code to handle controlEvents is: > >> > > >> > if (WrapperManager.isControlledByNativeWrapper()) { > >> > // The Wrapper will take care of this event > >> > } else { > >> > // We are not being controlled by the Wrapper, so > >> > // handle the event ourselves. > >> > if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) || > >> > (event > >> > == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) || (event == > >> > WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)) { > >> > log.warn("We are handling the received event > >> > ourselves > >> > and we are stopping the service"); > >> > WrapperManager.stop(0); > >> > } > >> > } > >> > > >> > I am using the wrapper integrated, that is I implement WrapperListener > >> > interface. > >> > > >> > Since I am running as a daemon, I don't want this to ever shut down, > and > >> > if > >> > does for some reason I would like it to auto restart (don't know how > to > >> > do > >> > this on Linux). > >> > > >> > Why might I be getting these JVM appears hung: Timed out waiting for > >> > signal > >> > from JVM. errors? > >> > > >> > -Dave > >> > > >> > > >> > > ------------------------------------------------------------------------- > >> > This SF.Net email is sponsored by the Moblin Your Move Developer's > >> > challenge > >> > Build the coolest Linux based applications with Moblin SDK & win great > >> > prizes > >> > Grand prize is a trip for two to an Open Source event anywhere in the > >> > world > >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >> > _______________________________________________ > >> > Wrapper-user mailing list > >> > Wra...@li... > >> > https://lists.sourceforge.net/lists/listinfo/wrapper-user > >> > > >> > > >> > >> > ------------------------------------------------------------------------- > >> This SF.Net email is sponsored by the Moblin Your Move Developer's > >> challenge > >> Build the coolest Linux based applications with Moblin SDK & win great > >> prizes > >> Grand prize is a trip for two to an Open Source event anywhere in the > >> world > >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >> _______________________________________________ > >> Wrapper-user mailing list > >> Wra...@li... > >> https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > > Build the coolest Linux based applications with Moblin SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event anywhere in the > world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
