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.

Bug 252031 - [81cat] Warning message "Profiler Agent Warning: JVMTI classLoadHook: class name is null" running the telemetry profile.
Summary: [81cat] Warning message "Profiler Agent Warning: JVMTI classLoadHook: class n...
Status: RESOLVED WONTFIX
Alias: None
Product: profiler
Classification: Unclassified
Component: Ide (show other bugs)
Version: 8.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-23 15:57 UTC by -Silver-
Modified: 2016-05-13 05:04 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description -Silver- 2015-04-23 15:57:51 UTC 
Step to reproduce:
1. Install NetBeans IDE Build 201504230001.
2. Open the test project memory leak or not used for cat 8.1 test
3. Clean and build the project
4. Into the project pane right click on the file Example2.java then select "profile file"
5. From the profiler dropdown button select "telemetry".
6. Press the button "Profile" to start the profiler.

The log reports many many times a warning message:
run-single:
Profiler Agent: Waiting for connection on port 5140, timeout 10 seconds (Protocol version: 16)
Profiler Agent: Established connection with the tool
Profiler Agent: Local accelerated session
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
[...]
Comment 1 Tomas Hurka 2015-04-23 17:10:32 UTC 
This harmless.
Comment 2 brettryan 2016-05-13 05:04:11 UTC 
While harmless, could we get the messages squelched? They do tend to clog up the logs.

Just like "MonitorFilter::WARNING: the monitor filter must be the first filter in the chain." would be good to have those squelched :)