|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Here is our current setup:
All servers are up-to-date running OS X 10.4.5 and the most recent version of WebObjects:
- Web Server also running WOMonitor
- App Server 1 [running production app]
- App Server 2 [running production app]
- App Server 3 [running test and batch app]
We statically reference the four servers in the apache config:
WebObjectsConfig http://172.16.1.11:1085,http://17.... Etc.
For some reason App Server 3’s wotaskd will stop responding. Sometimes this corresponds with high CPU usage, other times it’s somewhat random. However, when App Server 3’s wotaskd stops responding, it causes the web server to become extremely sluggish. My guess is that it is waiting to communicate with wotaskd on all app servers and this is causing the slowdown. As soon as I do one of the following combinations, it recovers: restart Apache on the web server, restart wotaskd on app server 4, restart app server 3.
I tried swapping the instances on App Server 2 and 3 (I made 2 run the test and batch apps and 3 run production) and the same wotaskd problems occurred but on App Server 2 now instead of 3. Now it is probably because of high CPU usage on the batch instance, which we need to look into. But why shouldn’t the apache module be able to handle one server that is not responding and keep processing requests quickly on the remaining good app servers?
Thanks in advance!
P.S. I also noticed in WOAdaptorInfo that it says the WebObjects Server Adaptor is 4.5.1. Is this correct and the most up-to-date adaptor?
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.