WebLogic Server Thread Pools
When a client connects to a WebLogic Server instance, the server (actually the socket muxer) places the request in the execute queue, along with the request's security and transaction details. Once a request joins the execute queue, an idle thread will execute the request and return the response to the client. If part of an application, such as an EJB component, blocks an execute thread for a long time, the server has no mechanism to kill that execute thread. If the application blocks many execute threads for any reason, the entire server execute queue slows down and will be unable to accept and process new client requests. The server simply runs out of free execute threads to assign to new requests.
The dedicated ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access