Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 174166

Summary: Profiling - no execution data was colllected after "reset data"
Product: z_Archived Reporter: Ben Tran <tranb>
Component: TPTPAssignee: Eugene Chan <ewchan>
Status: CLOSED FIXED QA Contact:
Severity: critical    
Priority: P1 CC: jkubasta, mjimenez, slavescu, vitaly.a.provodin
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: closed460
Attachments:
Description Flags
eclipse.ini with debug options
none
RAD 6.0 rationalsdp.ini
none
patch none

Description Ben Tran CLA 2007-02-14 09:56:14 EST
steps to reproduce:
- start server in profiling mode
- select java profiler, 
- add a profiling set, give it a name then select Execution Time Analysis
- select collect cpu time info and slect Show execution flow graphical details
- start monitoring
- load web page to be monitored
- stop monitor
- reset data on monitor
- start monitor
- load a different page to be monitored
- stop monitor
- open execution flow on the last monitor
- No data was collected
Comment 1 Eugene Chan CLA 2007-02-14 10:31:29 EST
Reset data performs a detach and attach actions behind the cover. In this case, the object creation data are collected in the first attach and their corresponding data are not loaded in the second attach. 

Marius, does the loader ignore data in the second attach when those data are associated to object created in the first attach?
Comment 2 Marius Slavescu CLA 2007-02-14 12:18:13 EST
Depends how you create the new agent, if it's not set in the loders' context it may not be used.

Please save the agents and zip the project and attach it here. 
Also would be good to see the raw data, use the attached eclipse.ini to collect the raw events in CURRENT_DISK_DRIVE:\messageValue* files, zip and attach those here also.

Comment 3 Marius Slavescu CLA 2007-02-14 12:20:03 EST
Created attachment 58980 [details]
eclipse.ini with debug options
Comment 4 Tatiana Jimenez CLA 2007-02-20 16:17:23 EST
Are there any instructions on how to use the aclipse.ini? thanks
Comment 5 Marius Slavescu CLA 2007-02-20 16:23:24 EST
Just replace the eclipse.ini from your eclipse folder with the one attached here, then run eclipse.exe.
Comment 6 Ben Tran CLA 2007-02-26 12:51:25 EST
Hi Marius,

I added -DModelDebugger.debugEventValue=true and 
-DCommunicationDebug.debugMessageValue=true to rationalsdp.ini but I could not find the CURRENT_DISK_DRIVE:\messageValue* files.  I attached my rationalsdp.ini file.  Note:  RAD 6.0 (Eclipse 3.0) uses rationalsdp.ini instead of eclipse.ini.) 
Comment 7 Ben Tran CLA 2007-02-26 12:52:13 EST
Created attachment 59806 [details]
RAD 6.0 rationalsdp.ini
Comment 8 Marius Slavescu CLA 2007-02-26 16:09:10 EST
I thought this was found in TPTP 4.0.

In RAD 6.0 you could use Profile to file and check if you get some data, make sure you set the profile file (you could probably use different files for each monitoring session) before each start monitoring.
Comment 9 jkubasta CLA 2007-03-20 13:12:51 EDT
updated sizing
Comment 10 Eugene Chan CLA 2008-03-13 18:41:21 EDT
'Reset Data' option is only available to JVMPI (JVM 1.4.*) profiling agent. And the problem is happening after the detach action. If I manually detach and reattach, I see the same behavior as reported where no further trace data is collected after the reattach action. I suspect something went wrong in the reattach scenario.
Comment 11 Eugene Chan CLA 2008-03-19 14:36:20 EDT
Debug in 
org.eclipse.hyades.trace.ui.internal.actions.NewSnapshotActionDelegate.run(TRCAgentProxy, INavigator) 
indicated that 
Object instance = LoadersUtils.locateAgentInstance(fAgent);
returns null and reattach fails to work.
Comment 12 Eugene Chan CLA 2008-03-19 15:12:00 EDT
Created attachment 92955 [details]
patch
Comment 13 Eugene Chan CLA 2008-03-19 15:19:04 EDT
fixed in HEAD.
Comment 14 Paul Slauenwhite CLA 2009-06-30 14:00:45 EDT
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.