[
https://issues.apache.org/jira/browse/KITTY-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Sacks closed KITTY-4.
-----------------------------
Resolution: Later
Assignee: Matthew Sacks
this is currently not a problem, and will come later once we get a plugin
architecture going for kitty, probably will come later on down the roadmap and
after our first release.
> method for diagnosing thread starvation
> ---------------------------------------
>
> Key: KITTY-4
> URL: https://issues.apache.org/jira/browse/KITTY-4
> Project: Kitty
> Issue Type: Sub-task
> Reporter: Matthew Sacks
> Assignee: 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
