On 11.5.2012 г. 16:56 ч., Felix Meschberger wrote: > 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 ? Felix, I agree that this could be very useful but I think that Web Console should still provide at least simple threads view that is compatible with ANY java vm. As for the lock support through JMX API... well, maybe we can finally import the JMX plugin that Christanto donated (see https://issues.apache.org/jira/browse/FELIX-3152).
I guess that if anybody needs to diagnose thread locks can use this plugin. In addition we can extend the plugin to automatically detect deadlocks based on the information it has, and provide it through a configuration printer. I must admit that my concerns about the JMX api, is that it does't run on older or embedded jvm. And at ProSyst we have a lot of clients using IBM J9 (Visual Age Micro Edition) and it doesn't have it. There are also a number of other VMs that don't support the latest Java 6 API. We have a lot of custom plugins and actively use Web Console as helper for developers. We find it a wonderful piece of software, but we need it to run everywhere - just like Java is supposed to do. Regards, Valentin > > 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 >> >> > > -- ------------------------------------------------- Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg ------------------------------------------------- stay in touch with your product. -------------------------------------------------
<<attachment: v_valchev.vcf>>
signature.asc
Description: OpenPGP digital signature
