This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I would be more interested in why those threads are getting stuck. The time taken to get a STUCK thread is around 10 mins. Why would a single servlet / thread process need more time ?
I am not aware of an automated way in which weblogic reports STUCK threads. What you can do however is to remotely connect to the JMX beans and determine if there are APIs exposed to collect this statistic. I think it should be possible.
I am not sure how work managers would help here. They do not provide any such notification service. They just help you to scale your work according to how much of it needs to be done.
We are using WL10MP1 .
We are getting few stuck threads in weblogic server files like <BEA-000337> <[STUCK] ExecuteThread
is there anything in settings weblogic where these things when appear can be reported automatically.
Or Is there any other options to do the same.
Hi man, what exactly do you want. You have few options on that using weblogic. You may configure an SNMP trap to send notifications to some tool. You can use WLST scripts to monitor your servers and than sen e-mails or sms. You can rely on WLDF (Weblogic diagnostic Framework) You can even program a java app with timers using JMX or WLST to monitor health.. An important thing is trying to find out what's the cause of this Stuck thread and solving it. You may use JRorckit Mission control for that or some other profiling tool.
In the following link, look for "Monitor your domain" where you'll find plenty information on these subjects for a start.