Locks don’t refresh properly after depth change

Type: Bug
Status: Reopened
Priority: 2 Major
Resolution:
Component/s: Admin Console
Labels:

Assignee: prodmgmt
Reporter: rdizmang
Created: September 05, 2008
Votes: 0
Watchers: 0
Updated:
March 19, 2010
Resolved:

Description

Launch the tc server Open the admin console Enable the lock profiler. Launch a TC enabled app which initializes shared roots.
Note the locks indicating the shared roots.

Change the stack trace depth Refresh

Note the locks are now missing from the listing.

Comments

Taylor Gautier 2008-09-09

This is as designed - changing the trace depth resets the stats.

The initial root locks that you saw will not be accessed again by that same client - so the second view is a view only of the locks acquired during the current “session”.

I have had a similar issue trying to remember if trace depth changes reset the stats - even though I helped design it! I think we need to make the UI more clear on this point.

So - while it’s working as designed - I would agree with you that the operation is obscure.

Fiona OShea 2008-10-08

Come up with better usability