Hi,
Has anyone ever had issues where Monitor has issues contacting wotaskd?
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?
First sniff the 1085 port on 192.168.1.25 to check if it's a network
problem, it should not.
Next step is to add debug like any other WebObjects applications to the
wotaskd and JavaMonitor by editing the launchd plist.
Add -WODebuggingEnabled YES -WOOutputPath /..../...log -NSDebugLevel 3
in the startup args (for full debug output you can add -NSDebugGroups -1)
it could give you some input on what's going on.
From my exprerience with one application being very slow, long response
times make the wotaskd unresponsive (in your case it could be on
startup/shutdown).
Also check in the logs for "java.io.IOException: Broken pipe" (it's not
a problem itself but usually a symptom of too long response time cause
Apache Adaptor close the TCP connection due to timeout)
Aurelien
_______________________________________________
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]
