On 22 Dec 2005, at 16:43, Chuck Hill wrote:
Hi William,
Check
/System/Library/WebObjects/Adaptors/Apache/apache.conf
See if you have the hosts listed as in
# Host List Configuration
# wotaskd is started automatically on supported platforms,
# so this is the default mode.
# The apache module gets its configuration from the wotaskds
# listed on the configuration line
# For multiple hosts:
# WebObjectsConfig http://<name-of-a-host>:<port-on-a-host>,http://
<name-of-another-host>:<port-on-a-host> <interval>
# For localhost:
WebObjectsConfig http://localhost:1085 10
It sounds like this may be missing the hosts of the machines that
the apps are running on.
Chuck
I have occasionally seen odd things when upgrading the OS. I'm used
to doing single-box deployment; the webserver and the application
server are all one and the same sole machine, called localhost. If
that machine begins being able to resolve its own name during bootup
(eg: somebody else upgrades the OS on an Xserve, which vends DNS to
other machines, such as this server) this confuses wotaskd and
friends mightily.
Fix #1: look at what's in /Library/WebObjects/Configuration/
SiteConfig.xml (or, if you're a total ObjC zealot like me, /Library/
WebObjects/Configuration/SiteConfig.conf ). What are the names of
your hosts? And the names of the hosts on which your applications
are running? Do they match the names you expect to see, either by
looking at the prompt shown in a Terminal.app window, or via internal
DNS and the like?
If not:
'sudo /System/Library/StartupItems/WebObjects/WebObjects stop'
Edit your site config file until everything's using a hostname your
expect to work
'sudo /System/Library/StartupItems/WebObjects/WebObjects start'
Fix #2:
I have never liked the scheme where the WebObjects Apache DSO polls
wotaskd to get a configuration. It has its merits when configuring
in deployment and when developing. I have encountered customer
networks where *something* is going on, and I have no clue what or as
to how it is bleeding into the appserver machine, which kills off TCP/
UDP traffic on port 1085. So, once everything's running nicely, I do
this:
curl http://localhost:1085/WebObjects/wotaskd.woa/wa/woconfig > /
Library/WebObjects/Configuration/WOConfig.xml
then edit /System/Library/WebObjects/Adaptors/Apache/apache.conf to
use the file configuration option instead.
But this is only good for me because I am managing a limited number
of apps/servers in a well-known and fixed configuration.
Being me, I have written shellscripts to automate flipping between
"host list" configuration and "file" configuration. And also a
shellscript fired off by 'cron' every hour to detect any process with
a suspiciously large number of TCP connections established to or from
port 1085, and kill them. If they're apps, wotaskd will restart
them; if they're wotaskd itself, woservice will restart it.
Hope this helps; your mileage may vary.
--
Patrick Middleton
OneStep Solutions plc
351 London Road Phone: +44 (0)1702 426400
Hadleigh Fax: +44 (0)1702 556855
Essex. SS7 2BT Email: [EMAIL PROTECTED]
England (MIME welcome)
_______________________________________________
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]
