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 159234 - NullPointerException at org.netbeans.modules.bugtracking.ui.issuetable.TableSorter.modelIndex
Summary: NullPointerException at org.netbeans.modules.bugtracking.ui.issuetable.TableS...
Status: VERIFIED FIXED
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Issuetracking Framework (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Stupka
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-26 16:23 UTC by Jaromir Uhrik
Modified: 2009-07-27 09:20 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 146790


Attachments
stacktrace (1.75 KB, text/plain)
2009-02-26 16:24 UTC, Jaromir Uhrik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaromir Uhrik 2009-02-26 16:23:55 UTC
Build: NetBeans IDE Dev (Build 090226)
VM: Java HotSpot(TM) Client VM, 1.5.0_16-133, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_16-b06-284
OS: Mac OS X, 10.5.6, i386

User Comments:
juhrik: Added issue to bugzilla via its web interface
In Ide pushed search (query contained the right added issue, but not sure whether it is the clue)
-->> the exception appeared



Stacktrace: 
java.lang.NullPointerException
        at org.netbeans.modules.bugtracking.ui.issuetable.TableSorter.modelIndex(TableSorter.java:316)
        at org.netbeans.modules.bugtracking.ui.issuetable.TableSorter.getValueAt(TableSorter.java:353)
        at javax.swing.JTable.getValueAt(JTable.java:1903)
        at javax.swing.JTable.prepareRenderer(JTable.java:3911)
        at javax.swing.plaf.basic.BasicTableUI.paintCell(BasicTableUI.java:2072)
        at javax.swing.plaf.basic.BasicTableUI.paintCells(BasicTableUI.java:1974)
Comment 1 Jaromir Uhrik 2009-02-26 16:24:05 UTC
Created attachment 77418 [details]
stacktrace
Comment 2 Tomas Stupka 2009-03-04 13:06:27 UTC
probably fixed in scope of b3a30c597f5b
Comment 3 Jaromir Uhrik 2009-03-16 11:42:37 UTC
Since I haven't seen this issue in last times I consider it as fixed.