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 51277 - Log message to messages.log as well for Target VM cannot load class to instrument
Summary: Log message to messages.log as well for Target VM cannot load class to instru...
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-08 14:49 UTC by jchristi
Modified: 2007-02-20 18:31 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 jchristi 2004-11-08 14:49:56 UTC 
It would be very useful to have these messages
noted to the messages.log file as well as having
each of these in a popup message in the IDE.
Comment 1 mishadmitriev 2004-11-09 01:58:32 UTC 
These messages are currently printed using System.err.println(). If I 
understand correctly, you would like them to be logged into some 
specially created file as well. This may not be easy, however, since 
the situation is not e.g. like a HotSpot crash (a one-time event; if 
it happens more than once it's perfect to record info in a new file 
every time it happens). In our case, these bad events may happen many 
times during one program execution, and every time you don't know 
whether it's the last one or not, or how many of them you had before. 
So you may end up with a zillion of files (each for one error), or 
just one big log file, with all reports, where possibly multiple 
application executions would be indistinguishable.

Thus I feel like providing this error log file and all the logic 
surrounding it would mean too much work for us for too little payoff. 
However, we may think about recording this and other error messages 
in the same NetBeans ide.log file - that would mean having all info 
in one place, and in much easier to analyze form. So thanks for 
letting us know about this problem!
Comment 2 jchristi 2004-11-09 03:08:30 UTC 
Yes, this is exactly what I meant, into the ide.log file.... only I 
think they renamed it to messages.log with Netbeans 4.0.

In NB 3.0 its stored here: c:\Document and 
Settings\<username>\.netbeans\3.6\system\ide.log

In NB 4.0 its stored here: c:\Document and 
Settings\<username>\.netbeans\4.0beta2\var\log\messages.log

Sorry for not being clear enough with my original description.

Thanks,
Jon
Comment 3 iformanek 2004-11-09 11:55:04 UTC 
This has been fixed by Misha's change related to bugfix of #51217
Comment 4 iformanek 2004-11-09 15:01:30 UTC 
This fix will be available in M3 v2
Comment 5 ehucka 2006-10-09 12:08:26 UTC 
Verification of old issues.
Comment 6 Alexander Kouznetsov 2007-02-12 22:38:26 UTC 
Closing old issues.
Comment 7 Alexander Kouznetsov 2007-02-20 18:31:28 UTC 
Reverting to the original Target Milestone value changed by mistake. Sorry for
inconvenience.