WebLogic Stuck Experiment 2014-11-14

Previous knowledge of WebLogic stuck is:

1. Will cause the system to be slow overall.

2. There will be a display in the WebLogic console centerline monitor.

3.weblogic uses a queue to process threads, the thread queue is scanned at intervals, the default is more than 600s is not finished in the log alarm (stuck), the console service will be alerted.

Today's question to verify: stuck thread if it's running all the time, if stuck too long will it be killed automatically? Scan stuck process will not be reported in each scan cycle stuck.

Lab Environment:jdk1.6 + WEBLOGIC10 + oracle10g

Destruction Scenario: now in the database, select * from test for update, and then write a select * from test for update on the JSP page.

Experimental results: every time you visit a JSP page, there are two stuck warning messages. And stuck threads are not automatically killed (wait three hours without being killed). The test table of the database is then unlocked, and no unstuck is reported in the log.

WebLogic Stuck Experiment 2014-11-14