When you start the WebLogic Managed Servers, the start-up process might not respond at times, and you might notice message similar to the following in the WebLogic administration-server log:

####<Oct 28, 2009 2:46:29 PM EDT> <Error> <WebLogicServer> 
<ctns6408.unx.sas.com> <AdminServer> <[ACTIVE] ExecuteThread: 
'81' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS 
Kernel>> <> <<1256755589019> <BEA-000337> <[STUCK] 
ExecuteThread: '100' for queue: 'weblogic.kernel.Default (self-tuning)' has been 
busy for "620" seconds working on the request weblogic.kernel.WorkManagerWrapper$1@1dfd1301", 
which is more than the configured time (StuckThreadMaxTime) of "600" seconds. 
Stack trace:

java.net.SocketInputStream.socketRead0(Native 
Method)
 
java.net.SocketInputStream.read(SocketInputStream.java:129)

Stuck threads in the administration server typically happen in two situations:

• at the time an application is installed
• at the time an application is started (initialization)

Stuck can also happen in managed servers. They tend to occur in application-specific scenarios, depending on usage, available memory, and so on.

Stuck-thread messages in the logs are an indicator that particular a request took more than 600 seconds to complete; it is not an exception. The request might take more than 600 seconds due to various external factors. It is fairly common for a SAS application to take more than 600 seconds to initialize and to enable the server to start.

If threads are stuck occasionally but no other problems appear, you do not need to be concerned. If you do see other issues or failures as well, focus on those problems first.

Although SAS Technical Support does not necessarily recommend it, you can configure the limit for stuck threads and tune them to reduce the number and frequency of messages to the log. For more details, see Oracle's online-help document Tuning stuck thread detection behavior.

Operating System and Release Information