![]() | ![]() | ![]() | ![]() | ![]() |
When you start your application server (IBM WebSphere, Oracle WebLogic or Red Hat JBoss), portlet deployment might fail. The error in the server log begins with the following message:
Exception in thread "PortletDeployer:sas.stp.alerts.par" Exception in thread "PortletDeployer:sas.url.par" java.lang.ArrayIndexOutOfBoundsException
If you search further into the exception, you will see duplicate lines that indicate interleaved stack traces. For example, you might see lines similar to the following:
SystemErr at com.sas.portal.container.deployment.Portletdeployer.addDeployedFile(PortletDeployer.java:138) SystemErr at com.sas.portal.container.deployment.PortletDeployer.addDeployedFile(PortletDeployer.java:138)
The thread-synchronization condition that generates this exception occurs rarely. Therefore, you might see the problem, but only sporadically.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Information Delivery Portal | Microsoft Windows Server 2003 Datacenter Edition | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Enterprise Edition | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Standard Edition | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Microsoft Windows XP Professional | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Microsoft® Windows® for x64 | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Windows Vista | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
64-bit Enabled AIX | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
64-bit Enabled Solaris | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
HP-UX IPF | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Linux for x64 | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Solaris for x64 | 4.2_M2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |