incubator-kitty-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Sacks (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KITTY-4) method for diagnosing thread starvation
Date Wed, 01 Jun 2011 01:50:47 GMT

    [ https://issues.apache.org/jira/browse/KITTY-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041935#comment-13041935
] 

Matthew Sacks commented on KITTY-4:
-----------------------------------

I think I am going to close this for now. This ties into the issue of adding modularity/plugins
to the application. I think we can re-investigate this once we've go our code cleaned up and
primary JMX CLI features intact.

> method for diagnosing thread starvation
> ---------------------------------------
>
>                 Key: KITTY-4
>                 URL: https://issues.apache.org/jira/browse/KITTY-4
>             Project: Kitty
>          Issue Type: New Feature
>            Reporter: Matthew Sacks
>            Priority: Minor
>
> we need a method to quickly diagnose the cause of thread starvation
> pidster September 08, 2010 | link | edit | delete
> The RequestProcessor's from the Tomcat JMX API, in combination with the ThreadMXBean
might work. The RPs are a pool, but if they're active, carry the Thread name - which ought
to be linkable to the Threads in the JVM beans. So if the threads are locked up & working,
we should be able to extract meaningful data.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message