Hello Anjo;
Also, I'd have guessed that the only reason an app doesn't respond is that has maxed out the thread pool or sth?
If the database is being flogged and isn't horizontally scalable, the system can be so unresponsive as to slow down one R-R cycle so much that it seems dead to the adaptor. Or another typical one is where the WOA is accessing a web-service and the far-end is so slow that the R-R cycle is slow and so the adaptor thinks the instance is dead. There's lots of ways to cause this!
Working-from-memory; I was playing with Apache-2 load-balancer / servlets a while back and I suspect that because it uses the well- defined "...?jsessionid=XXX" on the end of the URL to detect a session, it knows definitively when to make a request sticky to an 'instance' and when to load-balance it.
cheers. ___ Andrew Lindesay www.lindesay.co.nz _______________________________________________ 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]
