The application allows you to create threads which are busy or which are waiting long enough to be detected as 「stuck」 by WebLogic.session
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.app
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.less
What are hogging threads? When do threads become hogged? After what period of time?async
hogging_duration = scheduler 2 seconds , algorithmide