SUPPORT / SAMPLES & SAS NOTES
Problem Note 41402: An out-of-memory error occurs while working with alerts in the Emerging Issues workspace
 |  |  |  |  |
An out-of-memory error might occur while updating alerts, such as changing the alert status, in the Emerging Issues workspace. This problem occurs particularly when you apply multiple search criteria for alerts. The stack trace contains the following information:
java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:350) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:758) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:755) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2451) at com.sas.analytics.mfg.warranty.app.command.ThreadedCommand.runImpl(ThreadedCommand.java:47) at com.sas.analytics.mfg.warranty.app.command.BaseCommand.run(BaseCommand.java:69) at com.sas.analytics.mfg.warranty.app.command.BaseCommand.run(BaseCommand.java:45) at com.sas.analytics.mfg.warranty.app.ei.DefaultAlertCategoryDetailsPanel.pageChanged(DefaultAlertCategoryDetailsPanel.java:133) at com.sas.analytics.mfg.warranty.app.table.paged.PagedTableNavigationPanel.firePageChange(PagedTableNavigationPanel.java:431) at com.sas.analytics.mfg.warranty.app.table.paged.PagedTableNavigationPanel.setPageData(PagedTableNavigationPanel.java:221) at com.sas.analytics.mfg.warranty.app.table.paged.PagedTableNavigationPanel.setPageData(PagedTableNavigationPanel.java:205) at com.sas.analytics.mfg.warranty.app.table.paged.PagedTableNavigationPanel.setNavigationData(PagedTableNavigationPanel.java:191) at com.sas.analytics.mfg.warranty.app.table.paged.PagedTablePanel.onTableDataChanged(PagedTablePanel.java:700) at com.sas.analytics.mfg.warranty.app.table.paged.PagedTablePanel.setTableData(PagedTablePanel.java:278) at com.sas.analytics.mfg.warranty.app.ei.EmergingIssueTablePanel.setAlertTableData(EmergingIssueTablePanel.java:123) at com.sas.analytics.mfg.warranty.app.command.RefreshEmergingIssueAlertsCommand$2.run(RefreshEmergingIssueAlertsCommand.java:150) ... Caused by: java.lang.OutOfMemoryError
When the out-of-memory condition occurs, you must restart the application server.
The problem results from redundant operations that are using extra memory.
A workaround is to sort the alerts on alert keys prior to updating them.
- Open the Customize Columns dialog.
- Move the Alert Key column from the Available Columns list to the Selected Columns list. It is best to add the Alert Key column to the left of the Status column by placing it just above the Status column in the Selected Columns list. This way, you know where to look for it in the table. Click OK.
- Find the Status columns and place your mouse on the left edge of the column's header. Left-click then drag to the right to give the Alert Key columns some width.
- Either click the Alert Key column's header to sort that column, or use the Sort menu option.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Warranty Analysis | Microsoft Windows 2000 Advanced Server | 4.1 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Datacenter Server | 4.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Server | 4.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows Server 2003 Datacenter Edition | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Standard Edition | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| 64-bit Enabled AIX | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| 64-bit Enabled Solaris | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| HP-UX IPF | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||