On Nov 14, 2007, at 11:02 AM, Mike Schrag wrote:
That sounds odd to me. I am not sure why that would be. Is it
possible that the previous request for that instance timed out and
caused wotaskd to mark it as unresponsive? If so, the next
request would result in the session timeout message appearing
immediately.
I would have thought you'd get a No instance available (or the
redirect URL for that) under this condition rather than a session
timeout ...
Only if you only have one instance deployed. If there are multiple
instances, it will roll the request over to the next one. Which, if
a session is involved, immediately fails (assuming you have not
implemented mobile sessions).
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
