Re: Java Monitor Woes
Re: Java Monitor Woes
- Subject: Re: Java Monitor Woes
- From: "Jerry W. Walker" <email@hidden>
- Date: Thu, 8 Sep 2005 00:11:28 -0400
Hi, Calven,
Pierre Bernard sent a message to this list as follows:
From: email@hidden
Subject: [TIP] Application launch script wrapper
Date: September 2, 2005 9:47:36 AM EDT
In this message, he said:
========================
When deploying using WOTask/JavaWOMonitor we usually specify the path
to the application launch script. WOTask launches this script using
the SpawnOfWotaskd.sh script.
This script redirects standard and error output of the application
and its launch script to /dev/null. This makes live troubleshooting
harder than necessary. For one the output of the launch script is
lost. Having this however comes in handy debug an application that
refuses to start.
A great tool for debugging applications that hang is to send them a
QUIT signal. This makes the JVM write a full thread dump to the error
out put. Unfortunately this, by default, is also lost to /dev/null.
I thus wrote another wrapper script to the appliaction launch script.
This script redirects all output to a common log file. Rather than
replacing SpawnOfWotaskd.sh, I add another layer of indirection by
pointing WOTask to my launchApplication.sh script:
...
========================
Do a search for his message to get his script. If you can't find it,
let me know and I'll send you a copy. I think this may give you the
information necessary to debug your problem if Sacha Mallais's advice
doesn't help.
Regards,
Jerry
On Sep 6, 2005, at 3:33 PM, Sacha Mallais wrote:
On Sep 6, 2005, at 12:05 PM, Calven Eggert wrote:
Problem: WO application instances deployed via JavaMonitor (JM)
are not
starting up when Start/Stop button is selected. The status icon
animates the
ON switch, however none of the instances ever turn on. All
instances are
configured to Auto Recover and Scheduling is enabled.
Troubleshooting: Restarting the servers does nothing.
Within JM, deleting the configured application and re-configuring
each
instance does nothing. The app instances are still unable to turn ON.
Running the apps via terminal works. Hence, the frameworks and woa
files are
not the issue.
Current Solution: The above behaviour indicates that there is a
problem with Java
Monitor's configuration file; SiteConfig.xml. This file is located in
/Library/WebObjects/Configuration/SiteConfig.xml. I hesitate to
say that the
file is corrupt because it can be opened and the config details
appear
correct. However, deleting this file, restarting JM and
reconfiguring each
app and their instances solves the problem.
This solution is not ideal since you must manually reconfigure
each and
every app - which is painful if you have over 5 apps and 15
instances to
configure.
I don't know why/if SiteConfig.xml is getting corrupted, but it
might be worthwhile to do the following:
1) set things up in JavaMon as you'd like it
2) copy SiteConfig.xml to SiteConfig.xml.bak
3) next time you think SiteConfig.xml is corrupted, diff it against
this backup copy: diff SiteConfig.xml SiteConfig.xml.bak
That will at least show you the differences.
However, it seems unlikely that it is getting corrupted. Is there
anything useful in /var/log/webobjects.log?
sacha
--
Sacha Michel Mallais - Big Kahuna
Global Village Consulting Inc.: http://www.global-village.net/
Blessed is the WO-geek, for he shall inherit from NSEarth (Jobs 3:14)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40codefab.com
This email sent to email@hidden
--
__ Jerry W. Walker, Partner
C o d e F a b, LLC - "High Performance Industrial Strength
Internet Enabled Systems"
email@hidden
212 465 8484 X-102 office
212 465 9178 fax
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden