Additional functionality that is delivered in each maintenance release causes the memory footprint to grow. This memory footprint can exceed the current defaults for some systems, in particular WebLogic in 64-bit UNIX environments.

Vulnerable Systems

Distinguishing This Problem from Other Outages

There are many possible reasons that WebLogic can become unresponsive. In this case, the WebLogic logs show out-of-memory errors that mention a shortage of Permanent Generation (permgen) space. The error is similar to the following:

java.lang.OutOfMemoryError: PermGen space

Remedy

You must increase the size of the permgen for the JVM that is experiencing this problem. You can do this at installation time from within the SAS^® Deployment Wizard or after the installation is complete.

Modifying the Permgen during Installation

Run the SAS Deployment Wizard and select the custom configuration option that gives you access to the advanced prompts. When you select this option, you will see the Web Application Server: Managed Server labeled Additional JVM Options: text box on the panel. Enter the following parameter in that box:

Note that prior to the third maintenance release for SAS 9.2 (TS2M3), these options were added to the end of the command line. However, the Java Developer's Kit would always accept the last setting for the option on the command line.

Starting with the third maintenance release of SAS (TS2M3), the old option will be replaced and you will see only the new option once.

Modifying the Permgen in WebLogic during Post Installation

There are two ways to launch a WebLogic server and two places to maintain the server's command-line options.

• Configure Managed Servers through the WebLogic Administration Console

  If you start your server through the administration console or you use the WLST start command, the administration server maintains each server's command-line options in the config.xml file. You can view this file in your domain's configuration directory, but do not edit it manually if the administration server is running. Here are the steps to edit this information through the WebLogic Administration Console:

  1. In the Domain Structure panel, select Environment ► Servers.
  2. On the Summary of Servers page, select the link for the Managed Server to be configured.
  3. On the Settings for SASServerN page, select the Server Start tab.
  4. Edit the Arguments text box to add, delete, or modify options as necessary.
• Configure Managed Server Scripts
  • If you start your server directly from a command line or you use a Windows Service (not nodemanager service), you must modify the setDomainEnv script. Locate and edit the script for your domain:
    • bin/setDomainEnv.sh for UNIX environments
    • bin\setDomainEnv.cmd for Windows environments
  • Edit this file by adding or updating the MaxPermSize parameter, as follows:
    -XX:MaxPermSize=572m

    Note: If you perform an automatic configuration with the SAS Deployment Wizard or you follow the conventions in the sample domain, the MaxPermSize parameter is set as part of the USER_MEM_ARGS variable in the script.

  
  
  

  Operating System and Release Information

  Product Family	Product	System	SAS Release
  			Reported	Fixed*
  SAS System	BEA WebLogic Server	Solaris for x64	9.2 TS2M3
  		Linux for x64	9.2 TS2M3
  		HP-UX IPF	9.2 TS2M3
  		64-bit Enabled Solaris	9.2 TS2M3
  		64-bit Enabled AIX	9.2 TS2M3

  * 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.