Hi Valentin, Thanks for this.
One thing that has been nagging me over and over is lock information. This is not available throught the Java 5 API but through the Java 6 JMX API. How about addig this information (and mixing it into the stack traces as the plain-old Jack traces do) ? This might lead us to a point where we might be able to use our stack traces as input for stack trace tools like TDA. WDYT ? Regards Felix Am 11.05.2012 um 01:31 schrieb Valentin Valchev (JIRA): > Valentin Valchev created FELIX-3502: > --------------------------------------- > > Summary: Improve Threads web console printer > Key: FELIX-3502 > URL: https://issues.apache.org/jira/browse/FELIX-3502 > Project: Felix > Issue Type: Improvement > Components: Web Console > Affects Versions: webconsole-3.4.0 > Reporter: Valentin Valchev > Assignee: Valentin Valchev > Priority: Minor > Fix For: webconsole-3.4.2 > > > We can improve the Thread printer in a number of ways: > - it should be based on Sling thread printer : > http://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/threaddump/src/main/java/org/apache/sling/extensions/threaddump/internal/ > - it should call the Java 5+ methods via reflection, so it will work also in > older JVMs > - it should keeps sorting of the thread groups and threads by name > - It should be mode aware printer. > - In ZIP mode, the printer should also include thread dumps and class loader > information > - There will be a separate ThreadDumper class, that contains all logic for > printing threads/groups. It should be independent from the Web Console API so > it can be included by other projects. > > > > > -- > 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 > >
