weblogic之 hogging thread & stuck thread

最新推荐文章于 2021-01-13 13:42:32 发布

chuanximou9141

最新推荐文章于 2021-01-13 13:42:32 发布

阅读量643

点赞数

CC 4.0 BY-SA版权

原文链接：https://my.oschina.net/u/864135/blog/1358751

本文介绍了一个专门用于检测WebLogic 12c中死锁线程的小型应用程序。该应用通过创建忙碌或等待时间过长的线程来模拟卡住的情况，使用了简单的JSP页面设置参数，调用注入的状态less会话bean的异步业务方法。文章还探讨了hogging线程的概念及其在WebLogic中的表现。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

The application allows you to create threads which are busy or which are waiting long enough to be detected as “stuck” by WebLogic.

This little application will only work with WLS12c. I intentionally avoided JSF, so a plain JSP page is used to set your parameters. The JSP is calling a simple Servlet which in a for loop is calling an asynchronous business method of an injected stateless session bean. @Asynchronous and no-interface session beans are only available in EJB3.1 so you have to run it on WLS12c. Unlike in previous versions, the EJB is directly packaged into the .war file for deployment.

Depending on which method was called on the EJB is either waiting n seconds using Thread.sleep() or calculating some trigonometric function for n seconds. Both methods will cause stuck threads.

What are hogging threads? When do threads become hogged? After what period of time?

hogging_duration = scheduler 2 seconds , algorithm

转载于:https://my.oschina.net/u/864135/blog/1358751