On Aug 24, 2007, at 12:29 PM, Art Isbell wrote:
On Aug 24, 2007, at 8:53 AM, Chuck Hill wrote:
Is the the problem that Cliff posted a fix for?
If the ownership and permissions are correct, that would be the
next suspect.
The new machines are so fast that WO starts before the network
interfaces are initialized leading to its failure.
I haven't seen this on my 2.16 GHz Core 2 Duo iMac on which I've
replaced the WO startup item script with the OS X Server launchd
config files for wotaskd and JavaMonitor. While this mimics the
way WO services are started on OS X Server, there must be other
differences between OS X and OS X Server that result in this
problem not occurring under OS X.
Cliff's solution was to put a sleep in the startup script for WO.
With no WO startup item script on OS X Server, "sleep 5" should be
added as the first statement in the /System/Library/WebObjects/
JavaApplications/wotaskd.woa/wotaskd shell script.
Yes, that was it! Thank you. I was struggling to recall the details
of Cliff's fix.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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]
