SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 36085: Merging the last two bins in Interactive Binning node returns java.lang.NullPointerException error

DetailsHotfixAboutRate It

In the SAS® Enterprise Miner™ Interactive Binning node, you can split and join bins. However, if you split the last bin into two bins, and then join those two bins back together, you might receive the following java error on the Fine Detail tab:

An application error has occurred.

Clicking on the Details window returns the following:

java.lang.NullPointerException at com.sas.analytics.eminer.visuals.BinningDetailModel.getTMvalue(BinningDetailModel.java:2176) at com.sas.analytics.eminer.visuals.BinningDetailModel.getMenuItems(BinningDetailModel.java:1769) at com.sas.analytics.eminer.visuals.Binning$SelectionListener.valueChanged(Binning.java:1775) at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSelectionModel.java:187) at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSelectionModel.java:167) at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSelectionModel.java:214) at javax.swing.DefaultListSelectionModel.changeSelection(DefaultListSelectionModel.java:402) at javax.swing.DefaultListSelectionModel.changeSelection(DefaultListSelectionModel.java:411) at javax.swing.DefaultListSelectionModel.removeSelectionInterval(DefaultListSelectionModel.java:481) at javax.swing.DefaultListSelectionModel.clearSelection(DefaultListSelectionModel.java:416) at javax.swing.JTable.clearSelection(JTable.java:1261) at javax.swing.JTable.tableChanged(JTable.java:2907)

To avoid the error, do not split the last bin into two bins and then merge the bins back together.

Select the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Enterprise MinerMicrosoft® Windows® for 64-Bit Itanium-based Systems5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Microsoft Windows Server 2003 Datacenter 64-bit Edition5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Microsoft Windows Server 2003 Enterprise 64-bit Edition5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Microsoft Windows XP 64-bit Edition5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Microsoft Windows 2000 Advanced Server5.39.1 TS1M3 SP4
Microsoft Windows 2000 Datacenter Server5.39.1 TS1M3 SP4
Microsoft Windows 2000 Server5.39.1 TS1M3 SP4
Microsoft Windows 2000 Professional5.39.1 TS1M3 SP4
Microsoft Windows NT Workstation5.39.1 TS1M3 SP4
Microsoft Windows Server 2003 Datacenter Edition5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Microsoft Windows Server 2003 Enterprise Edition5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Microsoft Windows Server 2003 Standard Edition5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Microsoft Windows XP Professional5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Windows Vista5.36.1_M29.1 TS1M3 SP49.2 TS2M2
64-bit Enabled AIX5.36.1_M29.1 TS1M3 SP49.2 TS2M2
64-bit Enabled HP-UX5.36.1_M29.1 TS1M3 SP49.2 TS2M2
64-bit Enabled Solaris5.36.1_M29.1 TS1M3 SP49.2 TS2M2
HP-UX IPF5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Linux5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Linux on Itanium5.36.1_M29.1 TS1M3 SP49.2 TS2M2
Solaris for x645.36.1_M29.1 TS1M3 SP49.2 TS2M2
Tru64 UNIX5.36.1_M29.1 TS1M3 SP49.2 TS2M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.