Friday, November 6, 2009

Avoiding overload

in a nutshell:

* limit the number of execute threads with JVM properties:

* 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


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

No comments: