WebLogic ThreadPool has stuck threads throws a memory overflow __web

Recent projects have always been a problem, WebLogic nohup log file found in the following paragraph (red is the key), to the effect that the current request time is greater than the default request time, so you need to change the default request time to a larger point on the line, In fact, you want to modify the Stuckthreadmaxtime parameter in WebLogic.

<oct, 1:41:05 AM gmt+08:00> <Error> <WebLogicServer> <BEA-000337> <[stuck] Executethread: ' 2 ' for queue: ' Weblogic.kernel.Default (self-tuning) ' have been busy for "683" seconds working on the Reque St "Weblogic.work.selftuningworkmanagerimpl$workadapterimpl@24e924e9", which is more than the configured time (  Stuckthreadmaxtime) of "seconds". Stack Trace:
Null>
<oct, 1:43:05 AM gmt+08:00> <Error> <Kernel> <BEA-000802> <executerequest failed
Java.lang.NullPointerException.
Java.lang.NullPointerException
At Java.lang.Thread.setPriority (thread.java:817)
At Weblogic.work.ThreadPriorityManager.setThreadPriority (threadprioritymanager.java:207)
At Weblogic.work.ThreadPriorityManager.handleHogger (threadprioritymanager.java:226)
At Weblogic.work.RequestManager.getStuckThreads (requestmanager.java:919)
At Weblogic.work.ThreadPoolRuntimeMBeanImpl.getStuckExecuteThreads (threadpoolruntimembeanimpl.java:100)
truncated. See log file for complete StackTrace

>

Modify the Stuckthreadmaxtime parameter in WebLogic: Login to WebLogic's console-environment (environment)-Server (Servers), click on adminserver (Admin)--Configure ( Configuration)--Optimization (Tuning), as shown in the following figure

Similarly, overloading (overload), as shown below: