We are having a problem where it appears that JavaMonitor times out while waiting for a response from wotaskd.
We have JavaMonitor running on a tier1 machine and wotaskd running on the app server at tier2. This is the vanilla Apple versions, we haven't converted over to the Wonder versions in production yet. We turned on Deployment Debugging on both JavaMonitor and wotaskd. wotaskd appears to receive the monitor request, query the apps and then return the answer to the monitor. But if we watch the monitor output during that time, it sends out the request and then reports a timeout and connection error while wotaskd is still gathering information from its apps. Is there an option or property for JavaMonitor that tells it to wait longer for a response from wotaskd before throwing in the towel? This has never been a problem before, but I guess now that we have 20 instances running on that machine, it is taking longer than JavaMonitor is prepared to wait. We have a second app server that is running only 9 instances and it seems to be working fine. Jeremy ======================================================================= Jeremy Rosenberg Application Developer Institutional, Collaborative, and Academic Technologies IT Services Simon Fraser University Burnaby, BC, Canada V5A 1S6 Email: [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
