Hi guys, This is just a suggestion, which could simplify tasks of troubleshooting problems on live tomcat instance. It was so many times that I had to deal with request that seemingly hang having to go through every Thread's trace stack to find out what the hang request is stuck on. It would be great if "RequestProcessor" MBean has a reference to the Thread, which is dealing with the request in question by either ID or Name. (Name is preferred for backwards compatibility) We (as in LambdaProbe project) would link the "http request" to thread trace stack thus providing one mouse click resolution to the problem of stuck requests. Many thanks, Vlad
Do you want to submit a patch?
Created attachment 19820 [details] patch against the current http://svn.apache.org/repos/asf/tomcat/current/tc5.5.x
Created attachment 19821 [details] patch against the current http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk
Gladly :) The patches are attached. Both patches worked ok for me. I didn't know how Tomcat exposed request-related MBeans until today so please forgive me if i missed anything.
I hope it is not presumptuous of me to close this bug, but this was addressed back in March/April 2007 with r523235 (tc5.5.x) and r526576 (tc6.0.x).