[JBoss JIRA] Created: (JBAS-5079) Add a stuck thread feature to the application server that scans for stuck threads
by Jay Howell (JIRA)
Add a stuck thread feature to the application server that scans for stuck threads
---------------------------------------------------------------------------------
Key: JBAS-5079
URL: http://jira.jboss.com/jira/browse/JBAS-5079
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA
Reporter: Jay Howell
Many Other application servers have a stuck thread reaper that looks at threads and the times that they have been taking. If they take too long they are either logged as a warning or they are killed. This is a very dangerous safeguard, but it's a feature that does come in quite handy if a thread gets stuck on an object lock. We've seen some of these in support especially around the Jbosscache when customers misconfigure JbossCache with ejb3/hibernate. It also happens with customers do strange things with jms inside the app server.
The configuration might be something like.
StuckThreadInterval - interval at which the scanner should scan for stuck threads. Higher amounts will give more time before the event(log or inturrupt) is fired. -1 means it's disabled.
StuckThreadNotification - class to be called if a thread gets stuck default would be org.jboss....StuckThreadLogger
the default behavior should log the stuck thread.
But we should also have another class that can be plugged in the StuckThreadNotification that inturrups the thread. Maybe we can call it org.jboss.....StuckThreadInturrupter
Log should always log it, but with a configuration change, it should be able to inturrupt it.
We've had multiple requests for this feature.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[JBoss JIRA] Created: (JBAS-3877) The JMX HtmlAdaptor does not display the exception message
by Lior Shamir (JIRA)
The JMX HtmlAdaptor does not display the exception message
----------------------------------------------------------
Key: JBAS-3877
URL: http://jira.jboss.com/jira/browse/JBAS-3877
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JMX
Affects Versions: JBossAS-4.0.4.GA
Reporter: Lior Shamir
Assigned To: Scott M Stark
Priority: Minor
In JBoss 3.2.x when exception occurred, the HtmlAdaptor display the exception message.
In JBoss 4.0.x the HtmlAdaptor display only a generic error message.
This is obviously a regression. Can you add the message back?
Here is an example:
4.0.4:
javax.servlet.ServletException: Failed to invoke operation
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:269)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
javax.management.MBeanException
org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180)
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:258)
org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:262)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
3.2.6: javax.servlet.ServletException: Failed to invoke operation
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:248)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:79)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
root cause
MBeanException: com.koko.KOKOException: Invalid type
Cause: com.koko.KOKOException: Invalid type
org.jboss.mx.server.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:91)
org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:64)
org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:236)
org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:202)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:241)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:79)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months