History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-13625
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Michael Tokar [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Implicit profiling functionality broken

Created: 27/Sep/07 07:14 PM   Updated: 11/Oct/07 01:08 AM
Component/s: Administration, Performance
Affects Version/s: 3.0
Fix Version/s: 3.13

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Michael Tokar [Atlassian]
Since last comment: 42 weeks, 3 days ago
Labels:


 Description  « Hide
When you enable Profiling through the Administration interface in JIRA, it doesn't automatically reload the components already registered with the ComponentManager. Because it does not do this, the components are not wrapped by the Profiling dynamic proxy (TimerInvocationHandler), and thus all the implicit profiling that is supposed to occur (timing method invocations and so on) doesn't. Note that explicit profiling works as expected.

One way to get the implicit profiling to work after enabling profiling is to restore an XML backup of your instance's data. This operation reloads the ComponentManager and thus correctly wraps the components with the dynamic proxy.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.