[
https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649830#comment-13649830
]
Simone Tripodi edited comment on FELIX-3339 at 5/6/13 4:22 PM:
---------------------------------------------------------------
Hi [~cziegeler]! :)
If I am not wrong, Java7 and Java6 JXM APIs are exactly the same, so I
configured the main printer to fallback to the {{Jdk16ThreadDumper}}, in case
the JVM version is _1.7_, see the {{CompositeThreadDumper}} class in the patch.
Apologize for not having had a look at Java8 APIs, this is something I can
provide a new patch to fill that lack.
was (Author: simone.tripodi):
Hi [~cziegeler]! :)
If I am not wrong, Java7 and Java6 JXM APIs are exactly the same, so I
configured the main printer to fallback to the {{Jdk16ThreadDumper}}, see the
{{CompositeThreadDumper}} class in the patch.
Apologize for not having had a look at Java8 APIs, this is something I can
provide a new patch to fill that lack.
> 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
>
>
> 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
