[
https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274471#comment-13274471
]
Valentin Valchev edited comment on FELIX-3339 at 5/14/12 6:32 AM:
------------------------------------------------------------------
You maybe right. I'm changing to include the thread dumps by default it there
is just one on the same opinion!
It becomes messy if the thread dumps are included by default. You can barely
read the thread info - which thread belongs to which group. And if you need
basic overview of the running thread - there is no way to get it this way.
was (Author: v_valchev):
You maybe right. I'm changing to include the thread dumps by default.
> Consolidate Thread Dump Support
> -------------------------------
>
> Key: FELIX-3339
> URL: https://issues.apache.org/jira/browse/FELIX-3339
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-3.1.8
> Reporter: Felix Meschberger
>
> The Felix Web Console currently has an embedded plugin only using traditional
> Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs.
> These two should be consolidated and extended such that:
> * Separate bundle (not embedded in the Web Console Bundle)
> * one single plugin in Apache Felix
> * Uses Java 6 JMX API if available
> * Falls back to Java 5 JMX API if not Java 6
> * Falls back to regular Java API as a last step
> * Provide Gogo Shell Commands
> The advantage of using Java 6 API is to be able to inject lock information in
> the thread dumps to be able to followup on deadlock and similar situations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
