On Jun 27, 2008, at 6:37 AM, James Cicenia wrote:
Will this detect the "no instance available" message?
It will tend to prevent that message, because deadlocked instances will get killed, so you'll always have instances running. It can't guarantee that you'll have an instance available though, if you only have 2 and one is in "refuse new sessions" and one is deadlocked, you're going to get that message during the hour while the script is confirming that the instance is deadlocked. At that point, you need more instances.
If you're getting that a lot, you might want to set ERXTimeToKill on the command line (assuming you're using Wonder). What that does is set a watchdog timer once refuse new sessions is clicked on, so that no matter what the instance dies after a certain period of time. Otherwise, it's possible to have an instance stuck in refuse new sessions because it thinks a session is active that isn't.
Other ways to prevent this are turning on multithreading in your app, but that's not always easy to do if you haven't started out that way.
Pierce _______________________________________________ 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]
