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 48109 - "NullPointerException: Reference queue cannot be null" after upgrading JVM to 1.4.2
Summary: "NullPointerException: Reference queue cannot be null" after upgrading JVM to...
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Text (show other bugs)
Version: 3.x
Hardware: Macintosh Linux
: P3 blocker (vote)
Assignee: Petr Nejedly
URL:
Keywords: SIMPLEFIX
Depends on:
Blocks:
 
Reported: 2004-08-28 11:54 UTC by eppesuigoccas
Modified: 2008-12-22 16:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ide.log (beware: it is 22Mb long) (133.45 KB, application/x-gzip)
2004-08-28 11:57 UTC, eppesuigoccas 		Details
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 eppesuigoccas 2004-08-28 11:54:03 UTC 
I have been using NetBeans 3.6 with IBM JVM 1.4.1
for some months. Today I did find a problem in the
JVM and I had to upgrade to 1.4.2 (still from IBM,
powerpc 32bit version).
When running NetBeans I get many
"NullPointerException: Reference queue cannot be
null" during startup.
Comment 1 eppesuigoccas 2004-08-28 11:57:51 UTC 
Created attachment 17204 [details]
ide.log (beware: it is 22Mb long)
Comment 2 Petr Nejedly 2004-08-30 09:59:23 UTC 
A bug in openide/text. The code passes null queue argument to
Reference ctor, which is documented to throw NPE, but was never
implemented so (actually, the implementation does pass null internally
in some cases).

The same implementation was in IBM jdk till at least 1.4.1, but it
seems that IBM have fixed the implementation according to documentation...
Comment 3 Petr Nejedly 2004-08-30 12:24:32 UTC 
Fixed
openide/src/org/openide/text/PositionRef.java,v1.57
Comment 4 Marian Mirilovic 2005-12-20 15:48:29 UTC 
This issue was solved long time ago. Because nobody has reopened it neither
added comments, we are verifying/closing it now. 
If you are still able to reproduce the problem, please reopen. Thanks in advance.