Various fixes for Java/APache on isspoa2
07-Feb-07 14:02 |
ISS Norway
| Permalink
1. Looked throught the document "Application Server
Tuning for the E-Business Suite " by Ahmed Ahlomari,
Oracle, where there was a number of recommendations
that all have been implemented on the DEVL, OA_TEST and OA_PROD. Most notably is was _strongly_ recommended to upgrade to Java 1.5.0, and some suggestions from the Metalink Note: 275875.1 Oracle Application Framework Troubleshooting Release 11i (11.5.10) about raising the Java values when running into the error:
"Why am I getting java.lang.outOfMemory errors and what can I do to fix them?
OutOfMemory exceptions are thrown when the JVM runs out of heap space. Make sure that you have allocated enough memory for your JVM. Check the following entry in the jserv.properties file to make sure you the appropriate heap size range was specified. Here's an example of the how the heap size is specified in the jserv.properties file.
wrapper.bin.parameters=-Xms255m -Xmx400m
You should also make use of the AM Pool monitor to keep track of memory consumption as various applications are used. It will help you determine if the application is behaving abnormally, or if the JVM heap size needs to be adjusted."
that all have been implemented on the DEVL, OA_TEST and OA_PROD. Most notably is was _strongly_ recommended to upgrade to Java 1.5.0, and some suggestions from the Metalink Note: 275875.1 Oracle Application Framework Troubleshooting Release 11i (11.5.10) about raising the Java values when running into the error:
"Why am I getting java.lang.outOfMemory errors and what can I do to fix them?
OutOfMemory exceptions are thrown when the JVM runs out of heap space. Make sure that you have allocated enough memory for your JVM. Check the following entry in the jserv.properties file to make sure you the appropriate heap size range was specified. Here's an example of the how the heap size is specified in the jserv.properties file.
wrapper.bin.parameters=-Xms255m -Xmx400m
You should also make use of the AM Pool monitor to keep track of memory consumption as various applications are used. It will help you determine if the application is behaving abnormally, or if the JVM heap size needs to be adjusted."
|