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 79217 - ErrorManager rewrite rules introduces error icon behavior
Summary: ErrorManager rewrite rules introduces error icon behavior
Status: RESOLVED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-27 14:41 UTC by Jesse Glick
Modified: 2006-06-30 13:12 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2006-06-27 14:41:55 UTC
I have been bothered recently by a flashing error icon accompanied by the
strange stack trace

WARNING [global]
java.io.IOException: Owner timed out
	at sun.awt.X11.XSelection.getData(XSelection.java:348)
	at sun.awt.X11.XClipboard.getClipboardData(XClipboard.java:98)
	at
sun.awt.datatransfer.ClipboardTransferable.fetchOneFlavor(ClipboardTransferable.java:101)
	at sun.awt.datatransfer.ClipboardTransferable.<init>(ClipboardTransferable.java:80)
	at sun.awt.X11.XClipboard.getContents(XClipboard.java:84)
	at org.netbeans.core.NbClipboard.run(NbClipboard.java:218)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:519)
[catch] at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:951)

This is strange because none of those lines of code catch and print an
IOException. Finally I figured out that retrieving javaFileListFlavor throws
this exception sometimes and tracked it down to
DataFolder.FolderNode.getDraggedFilesList, which catches IOException and used to
read

ErrorManager.getDefault().notify( ErrorManager.INFORMATIONAL, ex );

but now reads

Logger.global.log(Level.WARNING, null, ex);

The former code definitely never showed the flashing error icon. It only printed
a stack trace. Apparently the new code does show the flashing error icon, which
is a regression. Please fix the rule, and consider reviewing that code you have
already changed by this rule. Or perhaps the default level required to show the
flashing icon needs to be changed, I am not sure.

(In this case I in fact plan to suppress the exception altogether, since it is
annoying and useless, but that is a different matter.)
Comment 2 Jesse Glick 2006-06-27 20:24:25 UTC
Thanks. BTW no milestones defined for apisupport/jackpot.
Comment 3 Jaroslav Tulach 2006-06-30 13:12:26 UTC
I've filled issue 79475 for the reordering problem of initCause and 
attachMessage.