Difference limiting HTTP sessions / throttling the pool (Weblogic12)?
Hi,
Weblogic requests are serviced through a single thread pool.
To avoid managing overloaded requests it is possible to throttle the thread by defining a maximum queue length.
What is the difference between limiting the HTTP sessions and throttling the thread pool?
How can we limit the HTTP sessions to avoid/control overload?
Thanks and regards.