[kepler-dev] [Bug 4960] New: NPE from TableSorter when repeatedly executing a small workflow in WRP

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4960

           Summary: NPE from TableSorter when repeatedly executing a small
                    workflow in WRP
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: ASSIGNED
          Severity: normal
          Priority: P2
         Component: workflow run manager
        AssignedTo: barseghian at nceas.ucsb.edu
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


If you're in the WRP suite and repeatedly execute a workflow, this NPE
sometimes occurs with each execution. WRM does not show up in the stacktrace,
but I'm fairly positive it's something to do with how WRM is using TableSorter.
Afaict this bug doesn't cause any harm (let me know if you notice otherwise).
Putting on 2.0 target since it's possible I may have to modify TableSorter:

[run] Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
[run] at util.TableSorter.modelIndex(TableSorter.java:289)
[run] at util.TableSorter.getValueAt(TableSorter.java:326)
[run] at javax.swing.JTable.getValueAt(JTable.java:1903)
[run] at javax.swing.JTable.prepareRenderer(JTable.java:3911)
[run] at javax.swing.plaf.basic.BasicTableUI.paintCell(BasicTableUI.java:2069)
[run] at javax.swing.plaf.basic.BasicTableUI.paintCells(BasicTableUI.java:1971)
[run] at javax.swing.plaf.basic.BasicTableUI.paint(BasicTableUI.java:1894)
[run] at javax.swing.plaf.ComponentUI.update(ComponentUI.java:154)
[run] at javax.swing.JComponent.paintComponent(JComponent.java:737)
[run] at javax.swing.JComponent.paint(JComponent.java:1000)
[run] at javax.swing.JComponent.paintChildren(JComponent.java:837)
[run] at javax.swing.JComponent.paint(JComponent.java:1009)

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.