Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (nike.apache.org: domain of fmeschbe@adobe.com designates
 64.18.1.181 as permitted sender)
From: Felix Meschberger <fmeschbe@adobe.com>
To: "dev@felix.apache.org" <dev@felix.apache.org>
Date: Fri, 11 May 2012 14:56:43 +0100
Subject: Re: [jira] [Created] (FELIX-3502) Improve Threads web console
 printer
Thread-Topic: [jira] [Created] (FELIX-3502) Improve Threads web console
 printer
Thread-Index: Ac0vfeXwe2zdFEZmTXyOjmhqm/DM2A==
Message-ID: <878DFA55-319C-45C5-A158-E9D4CA3FD764@adobe.com>
References: 
 <1708416168.53720.1336725109794.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1708416168.53720.1336725109794.JavaMail.tomcat@hel.zones.apache.org>
Accept-Language: de-DE, en-US
Content-Language: en-US
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

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 th=
e 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:
> ---------------------------------------
>=20
>             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
>=20
>=20
> We can improve the Thread printer in a number of ways:
> - it should be based on Sling thread printer : http://svn.apache.org/repo=
s/asf/sling/trunk/bundles/extensions/threaddump/src/main/java/org/apache/sl=
ing/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 loa=
der information
> - There will be a separate ThreadDumper class, that contains all logic fo=
r printing threads/groups. It should be independent from the Web Console AP=
I so it can be included by other projects.
>=20
>=20
>=20
>=20
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administra=
tors: https://issues.apache.org/jira/secure/ContactAdministrators!default.j=
spa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>=20
>=20