Re: WoMonitor "Failed to contact ..."
Re: WoMonitor "Failed to contact ..."
- Subject: Re: WoMonitor "Failed to contact ..."
- From: Sherry Tirko <email@hidden>
- Date: Thu, 19 Mar 2009 09:09:00 -0400
Hi Kieran,
What version of WO is on your Tiger server? If you are using 5.2.4,
you might be having a problem with close_waits. Apple calls it out as
a known bug with 5.2.3, but it seems to still linger in 5.2.4. We
found a reference about this online which I can't find at the moment,
sorry.
We were seeing the same problem. Our issue was caused by close_waits
that were building up on our server. If too many pile up, monitor will
have trouble communicating. The only way we know to get rid of the
close_waits is with a reboot.
Sherry
On Mar 18, 2009, at 7:09 PM, Kieran Kelleher wrote:
Well, 5 days later, it started again with this 'Failed to
contact..." business. So I added WOHost=ip.address params to wotaskd
Properties and relaunched wotaskd on each server ....... we will see
if it lasts 7 days this time with developing communications issues.
On Mar 14, 2009, at 2:31 AM, Chuck Hill wrote:
On Mar 13, 2009, at 7:20 PM, Kieran Kelleher wrote:
OK, I replaced the Bonjour names in the apache adaptor config with
IP addresses and configured those Leopard hosts with their IP
addresses instead of their Bonjour addresses in WOMonitor ..... so
the WOMonitor machine is no longer speaking French to the Leopard
XServes.
Thanks for the advice Chuck .... hopefully the next 7 days will
prove this to be more reliable. :-)
If not you can try adding -WOHost ip.address to wotaskd properties
or launchd config
Chuck
Regards, Kieran
On Mar 13, 2009, at 6:10 PM, Chuck Hill wrote:
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
--
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
_______________________________________________
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