Re: WoMonitor "Failed to contact ..."
Re: WoMonitor "Failed to contact ..."
- Subject: Re: WoMonitor "Failed to contact ..."
- From: Chuck Hill <email@hidden>
- Date: Fri, 13 Mar 2009 15:10:32 -0700
On Mar 13, 2009, at 3:00 PM, Kieran Kelleher wrote:
Hi All,
I recently upgraded 2 WebObjects-only XServes to OS X Leopard server
and the single XServe that runs apache/WebObjects and WOMonitor is
still on Tiger.
Since the upgrade I occasionally get situation where WOMonitor gives
the message:
Failed to contact omega1.local-1085
where omega1 is one of the servers running WO apps only.
Restarting everything will usually fix the problem, but as you can
imagine this is problematic. I really need to get to the bottom of it.
All apps are WO 5.3.3 fully embedded apps.
Anyone got any ideas on where to start?
..... Or, what is the root cause behind the message above? ...... or
what can I check to see what is wrong the next time it happens
(which is right now for one of the Leopard servers) before doing the
reboot fix.
That means JavaMonitor could not talk to the wotaskd process on
omega1.local. As an aside, I'd suggest not using Rondezvous, Bonjour,
or other French technology host names.. :-P They always seem
problematic for me. This error can mean it can reach the host on the
network, that wotaskd is listening to 1085 on a different hostname,
that the server was busy and the request timed out, that wotaskd was
busy, or there was a hiccup somewhere along the line. Often this
error happens once or twice then goes away.
Chuck
--
Chuck Hill Senior Consultant / VP Development
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-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden