EBS: R12 Default OACORE Memory Settings Are Not Enough

Default configuration

[applmgr@appshost01 scripts]$ cd $ADMIN_SCRIPTS_HOME
 [applmgr@appshost01 scripts]$ ./adoacorectl.sh status | grep "OC4J:oacore" | awk -F"|" '{print $3}' | while read L ; do ps -fp $L | grep -v PID ; done | awk -F"-X" '{print $2 $3}'
 mx512M ms128M
 mx512M ms128M
 [applmgr@appshost01 scripts]$

My suggestion

[applmgr@appshost01 scripts]$ grep s_oacore_jvm_start_options $CONTEXT_FILE
  ... -server -verbose:gc -Xmx2048M -Xms1024M ...
 [applmgr@appshost01 scripts]$

cd $ADMIN_SCRIPTS_HOME
 ./adautocfg.sh

./adopmnctl.sh stopall
 ./adopmnctl.sh startall

Side notes

• I do believe that if Java and applications' code would be bug-free, "s_oacore_nprocs" parameter should be set to 1 for most of the systems.
• However, Oracle instructs us to set an additional OARCORE process for all 200 users.
• In most systems I have worked with, the parameter was set to 2.
• Having multiple OACORE OC4J processes per environment makes it difficult to monitor the health of each container.
• If you know how to make sure that each of the OACORE containers generates a correct response (we typically check login screen using the text browser from our monitoring system), then please help me out and share your solution in the comments section of this blog post.

Emergency fix