Application access and upgrade issues on Solaris

This topic describes issues that you might encounter when you access or upgrade BMC Release Process Management (RPM) on a Solaris system.

This topic consists of the following sections:

HTTP status 500 error

When you use RPM on Solaris 10 with a remote PostgreSQL database, the HTTP status 500 error appears when you try to access the application from the browser.

Workaround: To use RPM on Solaris, reduce the memory amount used for the product service. If you plan to upgrade to a new version of RPM, reduce the memory amount used for the environment setup as described in procedures that follow.

To reduce the memory amount used for the product

1. Stop the RPM services.
2. Go to RLMhome\bin.

3. Open the start.sh file in a text editor.

4. Locate the line beginning with export JAVA_OPTS, and replace this line to the following:

    export JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx512m -XX:PermSize=256m"

5. Save your changes.
6. Start the RPM services.

To reduce the memory amount used for the environment setup

1. Go to RLMhome\bin.

2. Open the setenv.sh file in a text editor.

3. Locate the line beginning with export JAVA_OPTS, and replace this line to the following:

    export JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx512m -XX:PermSize=256m"

4. Save your changes.

Related topics

Accessing the interface

Performing the upgrade