On Apr 6, 2008, at 2:43 PM, Lachlan Deck wrote:
got a weird thing happening whereby some new deployed builds
successfully start up, so far as the logs are concerned, but Java
Monitor/wotaskd, can't see that it's up - and thus report a death.
Naturally you can't visit the site either.
Does "ps auxww | grep java" indicate that the instances that are
unavailable are actually running?
What response occurs when you try to access one of these apps? If
it's "No instance available", is the response immediate or after your
HTTP adaptor timeout period (30 seconds, by default)?
When viewing an app's instances in JavaMonitor, does JavaMonitor
report not being able to communicate with wotaskd?
If not using Mac OS X Server 10.5 and WO 5.4, have you inserted the
following:
#
# Verify network services are intialized before starting
#
echo Checking network services....
if [ "${PLATFORM_TYPE}" = "Darwin" ]
then
/usr/sbin/ipconfig waitall
fi
just before
#
# Launch the application.
#
in the wotaskd shell script in /System/Library/WebObjects/
JavaApplications/wotaskd.woa and /System/Library/WebObjects/
JavaApplications/wotaskd.woa/Contents/MacOS and the JavaMonitor shell
script in /System/Library/WebObjects/JavaApplications/JavaMonitor.woa
and /System/Library/WebObjects/JavaApplications/JavaMonitor.woa/
Contents/MacOS? This will prevent wotaskd, in particular, from
launching prior to the host knowing its IP address. Should this
happens, lots of deployment problems occur.
Aloha,
Art
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
