Weblogic Performance Tuning - Part 1 (Overload Protection)

[@shaiknazeer7307]

Thank you for your time & support 😍👍

[@digitak.middleware]

Stay connected

[@shaiknazeer7307]

@@digitak.middleware surely.

[@decaalv]

Agree. Very valuable information.

[@emransayed2137]

Thanks for post

[@digitak.middleware]

You're welcome

[@Santumudhol]

Thank you

[@digitak.middleware]

You're welcome

[@decaalv]

I had a situation where a specific EAR's threads were becoming in WAITING state, the number of threads in WAITING increased steadily, until eventually no more threads were ready for work. The cPU increased as the number of threads in WAITING state increased. How would you have troubleshooted that? My response was to restart the EAR and then everything flowed smoothly afterwards.

[@digitak.middleware]

How would you identify that a certain number of threads are in the waiting state for a specific ear application? If it's thread dumps and then Waiting reasons could be multiple, like the problem with DB due to some some locking, resource contention, long running queries, or maybe a problem with downstream applications if integrated etc etc. if everything is good, then you have to look from a tuning perspective especially number of threads per server, which you increase from default 400 to 500 or 600 and test

[@SwamyD-d2o]

if one of the datasources is overloaded what is the action plan ?

[@digitak.middleware]

If any one is overloaded then restart it.