On 12/08/2008, at 5:42 AM, Chuck Hill wrote:
On Aug 11, 2008, at 12:10 PM, Alan Zebchuk wrote:
Has anyone ever had issues where Monitor has issues contacting
wotaskd?
Has anyone not? :-P
We have 2 deployment servers, one of them running Monitor, and both
on 10.5 with 5.4.2 versions of wotaskd and Monitor.
All of the applications we're running are 5.3 with embedded
frameworks.
On one of the servers everything is fine, but for the other server
we often receive messages such as "Failed to contact
192.168.1.25-1085" (where 192.168.1.25 is the i of the other server.
As a result none of the applications that we have running on the
other server will respond to any requests.
This usually seems to occur when we try stopping or starting a WO
application on that server.
Any suggestions?
I'd carefully check the network. This might also be a timeout. I
don't recall if you can boost the timeout for this communication or
not. I've also seen it happen when the server is very busy, when
there are not enough file handles, or when free file system space
drops too low.
Wonder has versions of JavaMonitor and wotaskd that have bug fixes
and additional functionality. You might try those. If nothing
else, you could add some more debug logging.
Also check your reverse dns, hostnames etc.
See threads like 'Operation not permitted, very odd WO behaviour'
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
