' Weblogic.kernel.Default (self-tuning) problem WebLogic-level approach

Disclaimer: There are procedural aspects, network aspects, WebLogic settings, and so on, this article mainly describes the solution due to WebLogic settings.

Because:

1. The problem of the program, need to solve the project itself, WebLogic in the optimization process is also unhelpful.

2. Network interruption or the thought of closing the interaction is not handled with WebLogic (I think so.)

First, Description:

<2008-2-27 09:37 P.M. 48 seconds cst> <Error> <WebLogicServer> <BEA-000337> < Executethread: ' + ' for queue: ' Weblogic.kernel.Default ' have been busy for "1,720" seconds working on the request "Http Re Quest:/myapp/test/index.jsp ", which is more than the configured time (stuckthreadmaxtime) of" seconds.>  ";
2, number of threads (Tread count): The number of threads assigned to the Weblogic.kernel.Default queue. If you do not need to use more than 15 threads (the default), you do not have to change this property value.

     There are several ways to solve the: 
2) increase the number of threads to prevent thread blocking issues.
3) optimizer to reduce processing time.

Ii. Methods of Amendment

------------------------------------------↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ Amendments ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓---------------------------

1) How to modify the Stuckthreadmaxtime parameter value: http://lujinan858.iteye.com/blog/986237

Start the WebLogic service and go to the console:

your_domain->servers->your_server->configuration->tuning->stuck Thread Max time

Such as:

2) How to

Switch

Set java_options=%java_options%-dweblogic.threadpool.minpoolsize=50
Set java_options=%java_options%-dweblogic.threadpool.maxpoolsize=300

' Weblogic.kernel.Default (self-tuning) problem WebLogic-level solution