This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I used the remote profiler pack for profiling a J2EE application on BEA 8.1 App Server and I used the modified jdk 142. I am getting this error whether I tried to profile the entire application or a part of the application. I am unable to proceed further. ClassBytesLoader.getClassFileBytes ***Profiler agent critical error: could not get .class file for class $Proxy1 in ClassBytesLoader.getClassFileBytes ***Profiler agent critical error: could not get .class file for class $Proxy5 in ClassBytesLoader.getClassFileBytes ***Profiler agent critical error: could not get .class file for class $Proxy4 in ClassBytesLoader.getClassFileBytes ***Profiler agent critical error: could not get .class file for class $Proxy6 in ClassBytesLoader.getClassFileBytes ***Profiler agent critical error: could not get .class file for class $Proxy7 in ClassBytesLoader.getClassFileBytes ***Profiler agent critical error: could not get .class file for class $Proxy2 in ClassBytesLoader.getClassFileBytes ***Profiler agent critical error: could not get .class file for class $Proxy3 in ClassBytesLoader.getClassFileBytes
I am using Netbeans 5.0 Beta 2 with latest profiler m10 packs.
To complete the info: My BEA App Server has an Administration Server and a Managed Server. I set the profiler settings in the Managed Server start up file - startManagedWeblogic.cmd. Just being inquisitive: Is this a problem with Dynamic Proxies being used by the App Server code?
Created attachment 27086 [details] JVM error while doing CPU profiling for all classes.
Tired of trying to profile a remote application, I installed the application on my desktop and attempted local profiling on CPU without any success. Netbeans just flashes a message while trying to instrument – “Profiled Application not responding….Do you want to stop profiled application etc…etc”. I tried to do remote profiling again – choosing to profile all classes setting machine address to localhost. I get to see the classes and methods – but after some time the application collapses giving the error contained in the attachment. If I set a filter on classes being profiled, netbeans profiler fails saying that the profiled application is not responding. I have tried all options – and I am unable to do CPU profiling. Memory profiling works though. I am using Netbeans 5 Beta 2 with latest m10 packs for modified Jfluid jdk 142. And I have set the heap for the profiled application to 256m ( Xms ) & 512m ( Xmx)
We appologize for the problems, the bug is caused by the modified JVM. We are no longer developing the JFluid 1.4.2 JVM, and will not be able to fix this. Please update to Tiger for more stable profiling experience.
Verification of old issues.
Closing old issues
Reverting to original Target Milestone value changed by mistake. Sorry for inconvenience.