Release Notes › SOA Security Manager Release Notes › Known Issues › General Issues › Policy Server JVM Initialization Failure (61775)

Policy Server JVM Initialization Failure (61775)

The JVM required for some Policy Server features (such as the Session Server and XML key database) can sometimes fail to launch because it attempts to allocate too much memory.

Workaround

1. Navigate to the soa_home/siteminder/config directory.

   soa_home

   Specifies the SOA Security Manager installation location.

2. Open the JVMOptions.txt file in a text editor and add the following two lines anywhere in the file:

   -Xms256M
   -Xmx256M
   

   Note: The numeric component of each entry (which specify a memory allocation value in Megabytes) can be adjusted to suit your environment; however, it is recommended that both settings be set to the same value. For example, if the JVM needs more memory, you could set both values to 512.

3. Reboot the server.

(If the settings are inappropriate, an error message will be generated in the smps.log indicating that the JVM could not be initialized.)