Out of Memory Exception in OWSM

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

Comments

Post a Comment

Popular posts from this blog

jstatd error : Could not create remote object : access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write)

-
While running "./jstatd -J-Djava.security.policy=jstatd.all.policy &" command , below error is getting encountered Error :- Could not create remote object access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) java.security.AccessControlException: access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:536) at java.lang.System.setProperty(System.java:699) at sun.tools.jstatd.Jstatd.main(Jstatd.java:122) Cause :- The "access denied" error is expected, because "jstatd" requires a security policy file specified with the "java.security.policy" system property, if there is no security manager running on the machine. Solution :- 1) cd $ORACLE_HOME/jdk
Read more

Weblogic server is not starting up ; java.lang.AssertionError

-
  If the weblogic server is not starting up and giving the below error , please follow the below solution :- Error :- #Aug 18, 2014 12:34:29 AM PDT# #Notice# #WebLogicServer# #BEA-000365# #Server state changed to STARTING# #Aug 18, 2014 12:34:29 AM PDT# #Info# #WorkManager# #BEA-002900# #Initializing self-tuning thread pool# #Aug 18, 2014 12:34:29 AM PDT# #Notice# #Log Management# #BEA-170019# #The server log file /u01/app/oracle/config/domains/Vinay/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.# #Aug 18, 2014 12:34:29 AM PDT# #Critical# #WebLogicServer# #BEA-000386# #Server subsystem failed. Reason: java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine. java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.                 a
Read more

ORA-22990: LOB locators cannot span transactions

-
Below is the error reported in BPEL opmn logs :- ############ <2010-02-07 10:50:59,852> <:logerror>Error while invoking bean "cube engine": Cannot update lob column.The process domain was unable to update the lob column "3" in the datastore. The exception reported is: ORA-22990: LOB locators cannot span transactions Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid. sql statement: BEGIN INSERT INTO cube_scope( cikey, domain_ref, scope_bin ) VALUES ( ?, ?, '0' ) RETURNING scope_bin INTO ?; END; ORABPEL-04040 Cannot update lob column. The process domain was unable to update the lob column "3" in the datastore. The exception reported is: ORA-22990: LOB locators cannot span transactions Please check that the machine hosting the datasource is physically connected to the network. Oth
Read more