[
https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-3339.
--------------------------------------
Resolution: Fixed
Thanks Simo for your work. I have looked at it and continued tweaking it.
I have applied the following:
* Moved the Java 5 and 6 dependent classes to respective sub directories
* (Tried to) setup animal-sniffer. This fails because somehow I canot "ignores"
to work
* Cleaned all classes for Java 1.4, 5, and 6 compliance
For Java 1.4 only the threads can be dumped because Java 1.4 does not have API
to get at stack traces.
For Java 5 threads and their stack traces are dumped as well as any deadlocks.
For Java 6 threads and their stack traces are dumped along with held and
blocking locks; and of course deadlocks are printed as well.
The Java 5 and Java 6 dumps are compatible with TDA 2.2. If you have deadlock
information in the dumps, remove them before loading into TDA.
Committed in Rev. 1494960
> Consolidate Thread Dump Support
> -------------------------------
>
> Key: FELIX-3339
> URL: https://issues.apache.org/jira/browse/FELIX-3339
> Project: Felix
> Issue Type: Improvement
> Components: Thread Dumper
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: threaddump-1.0.0
>
> Attachments: FELIX-3339-FINAL.patch, FELIX-3339_initial-proto.patch,
> FELIX-3339_threaddump-as-inventoryprinter_FIXED.patch,
> FELIX-3339_threaddump-as-inventoryprinter.patch,
> FELIX-3339_threaddump-include-jdk18.patch,
> FELIX-3339_threaddump-smarter-jdk_version-comparison.patch,
> FELIX-3339_threadumper-output_compliant_hotspotVM.patch, Screen Shot
> 2013-05-23 at 3.02.24 PM.pdf
>
>
> 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
