If your Oracle application server 10.1.2 or Oracle Forms encounter the Java OutOfmemory issue, then you may need to changed your OC4J container java option in the opmn.xml to increase the heap memory. Add the following below , the start parameters and in the java-options.
data id="java-options" value="-Xms1024m -Xmx2048m -Xss256k "
The Xms specified the start of the heap memory , Xmx , specified the maximum memory settings for the java container. the Xss specified to set the maximum native stack size for any thread.
Starts from the 512m for the memory settings and the xss128k until the issue can be resolved.
After that, dcmctl updateconfig to update the configuration.
For more information, on the using of this Java parameters, please refer to
Fine-Tuning Memory Usage of 32-Bit Java on AIX
http://www.ibmsystemsmag.com/print/print.aspx?print_page=%2Faix%2Foctobernovember04%2Ftechnicalcorner%2F6643printp1.aspx&string_referer=/aix/octobernovember04/technicalcorner/6643p2.aspx
Forum on Java Outofmemory issue,
http://www.ibm.com/developerworks/forums/message.jspa?messageID=13853385
Metalink Note : 298551.1
OPMN and Process Monitoring
Metalink Note : 823504.1
What are the minimum and maximum sizes recommended for Java heap configuration for OC4J?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment