Profiler engine warning throws by Netbeans Memory Profiler

Question

I am trying to use Netbeans profiler, although I can run Profiler monitor but when I run Profiler Memory it shows the following errors in console under GlasshFish4 window.

*** Profiler engine warning: class sun.reflect.GeneratedConstructorAccessor107 that should be instrumented is not loaded by target VM
SEVERE:   *** Requested classloader: sun.reflect.DelegatingClassLoader@554f6057
SEVERE:   , its class = class sun.reflect.DelegatingClassLoader, index = 354, hashcode = 1431265367
SEVERE:   *** Profiler engine warning: target VM cannot load class to instrument sun.reflect.GeneratedConstructorAccessor107
SEVERE:   *** probably it has been unloaded recently
SEVERE:   *** Profiler engine warning: class sun.reflect.GeneratedConstructorAccessor108 that should be instrumented is not loaded by target VM
SEVERE:   *** Requested classloader: sun.reflect.DelegatingClassLoader@25bb0b75
SEVERE:   , its class = class sun.reflect.DelegatingClassLoader, index = 355, hashcode = 633015157
SEVERE:   *** Profiler engine warning: target VM cannot load class to instrument sun.reflect.GeneratedConstructorAccessor108
SEVERE:   *** probably it has been unloaded recently
SEVERE:   *** Profiler engine warning: class sun.reflect.GeneratedConstructorAccessor109 that should be instrumented is not loaded by target VM
SEVERE:   *** Requested classloader: sun.reflect.DelegatingClassLoader@44540a55
SEVERE:   , its class = class sun.reflect.DelegatingClassLoader, index = 356, hashcode = 1146358357
SEVERE:   *** Profiler engine warning: target VM cannot load class to instrument sun.reflect.GeneratedConstructorAccessor109
SEVERE:   *** probably it has been unloaded recently

http://stackoverflow.com/questions/20112666/how-to-interpret-profiling-results/20258821#20258821 — Vicky Thakor, Nov 29 '13 at 05:50
@VickyThakor thats my other question ! answer is not about this error. — J888, Nov 29 '13 at 05:57
What I meant is use `VisualVM` rather then netbeans's profiler — Vicky Thakor, Nov 29 '13 at 05:58
The problem by VM is that it does not show the name of project but glassfish only — J888, Nov 29 '13 at 06:00
do you know of any comprehensive tutorial that I can learn from ? — J888, Nov 29 '13 at 07:12

score 0 · Answer 1 · answered Jan 04 '14 at 12:23

These are not errors, per-se. These are warnings about the profiler engine not being able to transform various synthetic classes generated by the app server container. The profiler keeps on working just fine.

Also, switching to VisualVm wouldn't change anything since the same engine is used.

Profiler engine warning throws by Netbeans Memory Profiler

1 Answers1