StuckThreadMaxTime Error in the Logs (Doc ID 2995318.1)

Last updated on JANUARY 01, 2024

Applies to:

Goal

Customer often has errors due to stuckThreadMaxTime in the logs.

Example as it describes itself:

#### <wcsites_server2> <[ACTIVE] ExecuteThread: '75' for queue: 'weblogic.kernel.Default (self-tuning)'> <S Kernel>> <> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <[STUCK] ExecuteThre
ad: '60' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "654" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl
@35a9756e[GET /sites/Satellite]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
  java.util.HashMap$KeySet.iterator(HashMap.java:912)
  java.util.HashSet.iterator(HashSet.java:172)
  sun.nio.ch.SelectorImpl.processDeregisterQueue(SelectorImpl.java:145)

This happens often and it happens with different threads and tasks, while these errors appear, in their monitors longer query times appear.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.