I am using NetBeans Enterprise Pack build 060905 (which is built on top of
NetBeans IDE 5.5 Beta 2), NetBeans Profiler 5.5 Beta 2 and JDK 1.5.0_08.

I try to use the NetBeans Profiler to profile a second instance of NetBeans.

1. Start the first instance of NetBeans where the Profiler is installed.
2. Start the second (target) instance of NetBeans from command line like the
following:

C:\Alaska\nb_all\nbbuild\netbeans\bin>.\nb.exe
-J-agentpath:"C:\Progra~1\netbeans-5.5beta2\profiler1\lib\deployed\jdk15\windows\profilerinterface.dll=\"C:\Progra~1\netbeans-5.5beta
2\profiler1\lib\"",5140

Got the following in the stdout:

Profiler Agent: Initializing...
Profiler Agent: Options: >C:\Progra~1\netbeans-5.5beta2\profiler1\lib,5140<
Profiler Agent: Initialized succesfully
Profiler Agent: Waiting for connection on port 5140 (Protocol version: 2)

3. Inside the first NetBeans instance, select Profile->Attach Profiler..., 
4. Select Analyze Performance (on part of application)
5. Specify a root method, which, in my case is
org.netbeans.modules.compapp.test.ui.actions.AddTestCaseAction.performAction(Node[]
activatedNodes).
5. Select quick filter to include "org.apache.xmlbeans.*"
6. In the Attach Wizard, select "Application" as target type, "Local"
application location, "Direct" attach method, "Manual" integration type, and JDK
5.0_04+
6. Click "Attach"
7. The second NetBeans instance starts up and everything looked fine.
8. Somewhere down the line, the second NetBeans instance froze and this is what
I had on its stdout:

Profiler Agent: Established local connection with the tool
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent Warning: Failed to lookup cached class build_impl
Profiler Agent Warning: Failed to lookup cached class build_impl$0


In step 4, if I select Analyze Performance on the whole application, I would get
the "Failed to lookup cached class" error much earlier, actually during the
splash screen stage.

Profiler Agent: Initializing...
Profiler Agent: Options: >C:\Progra~1\netbeans-5.5beta2\profiler1\lib,5140<
Profiler Agent: Initialized succesfully
Profiler Agent: Waiting for connection on port 5140 (Protocol version: 2)
Profiler Agent: Established local connection with the tool
Profiler Agent: Redefining 100 classes at idx 0, out of total 372
Profiler Agent: Redefining 100 classes at idx 100, out of total 372
Profiler Agent: Redefining 100 classes at idx 200, out of total 372
Profiler Agent: Redefining 72 classes at idx 300, out of total 372
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent: 250 classes cached.
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
Profiler Agent Warning: Failed to lookup cached class build_impl
Profiler Agent Warning: Failed to lookup cached class build_impl$0
Profiler Agent: 250 classes cached.