Avoiding overload

http://download.oracle.com/docs/cd/E12839_01/web.1111/e13701/overload.htm


in a nutshell:

* limit the number of execute threads with JVM properties:
-Dweblogic.threadpool.MinPoolSize=x
-Dweblogic.threadpool.MaxPoolSize=y

* create a Network Channel and assign to it a "Maximum Connected Clients"

* in configuration / overload, set "Shared Capacity For Work Managers"

* for WebApps, set the max-in-memory-sessions in the deployment descriptor

* create a global Work Manager called default, and assign constraints to it

(see http://download.oracle.com/docs/cd/E11035_01/wls100/config_wls/self_tuned.html)


In post 8.1 WebLogic, the threads belong to a unique queue weblogic.kernel.Default.