I am using YourKit to profile an application running on Weblogic 8.1.
I connect to the application remotely and am able to successfully use the CPU sampling. When I start method level tracing I receive an error popup:
Assertion failed: cpuInfo->myEntryCount !=0, file EventHandler.cpp line 121.
Windows 2000 Professional
WebLogic 8.1 sp2
JDK 1.4.2_06
TibcoEMS 4.1.10
YourKit 4.0.8 (build 554)
Assertion failed: cpuInfo->myEntryCount !=0
-
- Posts: 1624
- Joined: Tue Aug 10, 2004 7:52 pm
-
- Posts: 2
- Joined: Thu Apr 21, 2005 10:07 am
Vladimir,
The assertion fails as soon as I connect the profiler. It is reproducible every time, I can connect/disconnect/reconnect with CPU sampling but as soon as I connect with method level tracing the assertion failed error occurs.
If I can provide any other information that would be of use please let me know.
Regards,
Paul
The assertion fails as soon as I connect the profiler. It is reproducible every time, I can connect/disconnect/reconnect with CPU sampling but as soon as I connect with method level tracing the assertion failed error occurs.
If I can provide any other information that would be of use please let me know.
Regards,
Paul
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Hello Paul
Thank you very much for the details. Unfortunately we didn't manage to reproduce the problem. Analyzing the code, we also have no idea how (even theoretically) this assertion can happen.
Could you please try the following:
1. Make sure the agent is indeed from build 554. To do this, please check the line in console of profiled application that should be like
[YourKit Java Profiler xxx]
2. Is this problem reproducible with any other Java application on your machine? E.g. could you please try SwingSet2 standart JDK demo.
3. If it is possible, could you please try running your application with any other Java version to see if it makes any difference.
Best regards,
Anton
Thank you very much for the details. Unfortunately we didn't manage to reproduce the problem. Analyzing the code, we also have no idea how (even theoretically) this assertion can happen.
Could you please try the following:
1. Make sure the agent is indeed from build 554. To do this, please check the line in console of profiled application that should be like
[YourKit Java Profiler xxx]
2. Is this problem reproducible with any other Java application on your machine? E.g. could you please try SwingSet2 standart JDK demo.
3. If it is possible, could you please try running your application with any other Java version to see if it makes any difference.
Best regards,
Anton
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am