felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-3339) Consolidate Thread Dump Support
Date Mon, 06 May 2013 17:56:16 GMT

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

Simone Tripodi commented on FELIX-3339:
---------------------------------------

Sure, I'll investigate on what you suggested and propose a patch!
                
> 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
>         Attachments: FELIX-3339_initial-proto.patch, FELIX-3339_threaddump-include-jdk18.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message