SOA Suite – Out Of Memory Exception

Posted: June 18, 2008 in HowTo, Oracle
Tags: , ,

10.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

10.2.1 NFS-Mounted Installations

You may encounter an error when installing Oracle WSM on an NFS-mounted device. This error is the result of a timing problem on NFS-mounted devices and occurs during the running of the Oracle WSM Configuration Assistant. The error you see will be similar to the following:

dataload-clean;
delete] Deleting directory ORACLE_HOME/product/instance_name/owsm/db
BUILD FAILED
ORACLE_HOME/product/instance_name/owsm/scripts/install.xml:1971:
The following error occurred while executing this line:
ORACLE_HOME/product/instance_name/owsm/scripts/dataload.xml:159:
Unable to delete directory
ORACLE_HOME/product/instance_name/owsm/db
...

To work around this problem, complete the following procedure:

  1. Edit the ORACLE_HOME/owsm/scripts/dataload.xml file.
  2. Edit the following line:

    <delete dir="${dataload.generateSql.rootDirectory}" />

    Add the text in bold to this line:

    <delete quiet="true" dir="${dataload.generateSql.rootDirectory}" />

  3. Click Retry to continue configuring Oracle WSM.
  4. After you have successfully configured Oracle WSM, delete the following directory: ORACLE_HOME/owsm/db.

10.2.2 XE DB Settings

Using an Oracle XE database with Oracle WSM may present connection problems. This is a known error that sometimes occurs with Oracle XE database client, but presents an intermittent problem for Oracle WSM.

To work around this limitation you may need to increase the value of the database parameter PROCESSES. The default value for this parameter setting is 40, but you may try to increase the value to 64. If required, you can further increase the value of this parameter.

10.2.3 Out of Memory Exception

You may get an out of memory exception if the Oracle WSM is configured so that its runtime memory requirements exceed the JVM default configuration. One known situation where this can occur is if you patch Oracle WSM 10.1.3 to 10.1.3.1.

To avoid this error, you need to increase the size of the Java heap.

To change the values of the Java heap

  1. Log in to Oracle Enterprise Manager 10g Application Server Control.
  2. In the Cluster Topology page, locate the Members section, and click home.
  3. Click Administration.
  4. Find Server Properties in the Task Name list, and click the Go to Task icon.
  5. Edit the values for Maximum heap size (1024 Mb) and Initial heap size (512 Mb).
  6. Add a row for the -XX:MaxPermSize (256 Mb) and -XX:PermSize (128 Mb) parameters and provide a value.
  7. Click Apply.
  8. Restart the server.

Note:

The values in parentheses are provided as an example only. These values were derived assuming that all components in the Oracle Application Server 10g Release 3 (10.1.3.1.0), also known as the Oracle SOA Suite (10.1.3.1.0), are installed. Consult your OC4J administrator and the Oracle Application Server Performance Guide for the appropriate settings for your environment.

10.2.4 Web Browser Times Out

In situations where there is high network latency between Oracle WSM and Oracle Database, the Web browser may time out before it can retrieve the data from the database.

To prevent the browser from timing out, modify the browser time out setting.

For Internet Explorer

  1. Edit the following registry key:

    HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Internet Settings

  2. Add the DWORD KeepAliveTimeout, and set the value in milliseconds.

For all other supported Web browsers, please consult the product documentation for the browser for information on setting the browser time out.

10.2.5 Oracle Access Manager SDK Path

When you configure the Oracle Access Manager Authenticate Authorize policy step, and you reconfigure the path to the Oracle Access Manager SDK, the new path does not take effect until you restart any agents or gateways that use this SDK.

Note:

Oracle Access Manager SDK is the same as what has previously been referred to as Access Server SDK.

10.2.6 Invoking Service from a Proxy Server

You may experience problems when invoking a service, located on the nonproxy host, from a proxy server even though you have configured the settings correctly. This may occur with a standalone installation of Oracle WSM or when Oracle WSM is installed as part of the Oracle SOA Suite.

To work around this limitation, delete the proxy.host and nonproxy.host settings in the properties files.

  • If you have a standalone installation of Oracle WSM, delete the settings in the ORACLE_HOME/owsm/bin/coresv.properties file.
  • If Oracle WSM is installed as part of the Oracle SOA Suite, delete the settings in the ORACLE_HOME/opmn/conf/opmn.xml file.

For more information about setting these properties, see the Oracle Web Services Manager Deployment Guide, or Section 10.3.4, “Correction to Command Syntax”.

Comments
  1. Very good blogging about SOA suite. I think it is Oracle bug. Out of memory..Aha good resolution has been provided. Thanks buddy.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s