Community
Participate
Working Groups
This is a pretty specific defect but it is affecting my tests. In AGR standard mode, a test of a probe Insertion Profile will hang at 51% giving errors in the agent controller's log file that I will attach. In quick mode these pass as well as when launching the same workbench in debug or standard mode and then manually executing the Profile. Navid, can you add any other occurrences where you are seeing a hang at 51%? I can't reproduce in the may 8 driver except in this one circumstance. If this proves to be the only case then I am willing to wait on this being fixed as I can run my tests for the test pass in quick mode (the verifications are file output comparisons so it won't take a lot longer).
Created attachment 66337 [details] Log File for error in Probe Insertion JVMTI I have attached the log
I've also experienced this problem intermittently when working with the Agent Controller.
Liz, can you rerun with the AC logging set to Simple instead of CBE and also the level of logging to be DEBUG. Can you elaborate as to how you root caused this to JVMTI vs. other components. The reason I ask is because I have seen a number of defects where in the AC stalled during execution
Hi Guru, I have not root caused this to the JVMTI agent. However, I feel this is agent-related. It may be with the AC and/or with the probekit agent extension although Navid reports this with other JVMTI analysis types. I will reset those log parameters and attach. Thanks for looking into it. Like I said, its not critical for me at this stage.
Created attachment 67111 [details] Log file with DEBUG and CBE format Please find attached the requested log file. Eugene, can you comment on whether you have run into this? I am wondering if it could be a configuration problem on my end.
Raising severity as I think this defect should be fixed in i4.
I see the same error for JVMPI
In light of Cindy's comment Guru please re-assign to the AC Team.
(In reply to comment #2) > I've also experienced this problem intermittently when working with the Agent > Controller. Navid, what a test case are you using?
Igor, I've noticed this problem from time to time when profiling a simple Java application.
I see the same problem while manually profile a java application using RAC4.3.1 on all other platforms.
*** Bug 187399 has been marked as a duplicate of this bug. ***
Created attachment 69085 [details] patch Hi Samson, Could you please review the patch? I've tested it on Vista, Win NT, and Linux. Thanks.
Hi Igor. Patch looks good. Please request for approval. Thanks.
Thanks Igor, I appreciate it!
(In reply to comment #14) > Hi Igor. Patch looks good. Please request for approval. Thanks. Hi Samson, the patch is approved. Could you check the patch in?
Patch checked in. Igor, you can mark this as fixed. Thanks.
fixed
(In reply to comment #15) > Thanks Igor, I appreciate it! Hi Liz, could you test the patch? Does it work for you?
I will test it with the driver that comes out today and report back to the defect.
I am seeing the same 51% hang in the 200705310943 driver. I will attach an AGR test suite you can use to validate.
Created attachment 69784 [details] Sample Test Case Please find attached a sample test suite showing the problem. You can run this one as-is (I have only enabled one test case) in standard mode with Java5 to see the process hang at 51%. Please let me know if you need anything else.
(In reply to comment #22) > Created an attachment (id=69784) [details] > Sample Test Case > Please find attached a sample test suite showing the problem. You can run this > one as-is (I have only enabled one test case) in standard mode with Java5 to > see the process hang at 51%. Please let me know if you need anything else. Liz, I've never work with AGR before. Could you please give me details. What do I need to reproduce the defect?
1) Open a fresh workspace 2) Create plugin project (File > New > Project > Plugin Project (complete the required fields) 3) Import the attached test suite into this plugin project 4) Ensure the AC or IAC are running 5) Select the test suite (right click) and select Run As > Test 6) You will see a new runtime workbench open where the test suite will playback events. Note that there are some intentional pauses in the execution. The correct outcome would be for it to launch a profile The actual outocome is that the profile gets stuck at 51%. If you use the mouse or change the focus of the runner in any way the test case will fail. You need to allow the runner to have control over the UI while the test is executing.
Hi Liz, I can't import test case you attached (How can I do it?). I recorded and successfully playing back my own ui test with profiling session on remote machine. Could you repeat you test with the last AC build from June 7th? Your issue might be caused by too short timeout value for process launching. Currently it is set in execution framework to 5 seconds only. If issue remains, it could be reasonable to increase timeout value.
Created attachment 70490 [details] Test case
Hi Igor, I have sent you the test case in .testsuite form via email. You should be able to just import it as a General File system import in Eclipse: File > Import > General > File System> Browse to it, import. This only fails when running AGR tests as described belwo. Manual profiles on a remote machine will pass.
Created attachment 70767 [details] patch #2 Hi Samson, could you please review the patch? It fixes stack memory violation. Tnanks. Liz, With this patch I've successfully launched your (bit modified) AGR test suite.
I tested the patch after some difficulties and it does allow a process to be launched. Thanks for your hard work.
Fix checked into CVS 2007/06/12 13:16 EDT.
Verified in TPTP 200706140100 driver
Closing
