RE: [Wrapper-user] wrapper executable fails to restart JVM

[Sal I. <sal...@sy...>]

at my old job we never ran the wrapper but we did run java/weblogic.

our java process would simply die for no reason, and even simultaneously
across networks!

we had one network in NY running production & one in CA running qa.

servers in both time zones would die simultaneously.

we were going crazy & did a ton of research.

after weeks of dealing with weblogic, we got escalated to a tech who told us
to run the java process with NOHUP.

so instead of running
java MyApp
run
nohup java MyApp

nohup is unix utility that ignores kill signals from the OS.

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Patrick
Woodworth
Sent: Monday, January 05, 2004 11:45 AM
To: wra...@li...
Subject: Re: [Wrapper-user] wrapper executable fails to restart JVM



To follow up with a little more info in case it's of any use.  We've
been running duration tests with the debug output on, on a number of
boxes for two weeks, but haven't seen this problem on any of them.  We
recently reinstalled the application on one box but forgot to turn the
debugging output on, and of course 21 hours later the JVM process was
gone.  The log snippet from the previous email is from that failure.
We've now turned debugging on again, but it's not clear whether we can
reproduce the problem with debugging on.


--- Patrick Woodworth <wo...@em...> wrote:
> I'm using the wrapper to run a service and I'm seeing odd behaviour
> on
> two Solaris 8 boxes.  Basically the java process dies and goes away.
> The wrapper executable is still running but never restarts the JVM.
> This has happened on two different boxes, sometimes after running for
> 2
> weeks and sometimes after only 21 hours or so.  Unfortunately I
> haven't
> been able to reproduce the error with debug flags on, but below is a
> snippet of what does appear in the log file.  Basically the first
> line
> of the snippet is the last thing sent to the log before manual
> intervention.  The rest of the snippet occurs after we noticed the
> JVM
> process no longer existed and we manually told the wrapper to
> restart.
> Any suggestions on what this might be?
>
> INFO | jvm 1 | 2003/12/31 10:14:43 | WebApplication: SETUP COMPLETED.
> STATUS | wrapper | 2004/01/02 13:43:54 | Shutting down.
> INFO | jvm 1 | 2004/01/02 13:43:54 | Wrapper Manager: The Wrapper
> code
> did not ping the JVM for 30 seconds. Quit and let the Wrapper
> resynch.
> INFO | jvm 1 | 2004/01/02 13:43:54 | Stopping service
> Tomcat-Standalone
> INFO | wrapper | 2004/01/02 13:43:54 | Wrapper Process has not
> received
> any CPU time for 104525 seconds. Extending timeouts.
> STATUS | wrapper | 2004/01/02 13:43:54 | <-- Wrapper Stopped
> DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning intermediate
> process...
> DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning daemon process...
> STATUS | wrapper | 2004/01/02 13:43:59 | --> Wrapper Started as
> Console
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for
> IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user