In Fusion Middleware 11g you’d normally set your Java memory arguments by specifying the USER_MEM_ARGS variable (in the <DOMAIN_HOME>/bin/startWeblogic.sh for example). The effect of this is that whatever magic happens in the scripts like setDomainEnv.sh, in the end the memory settings will be set like you’ve set in USER_MEM_ARGS.
Is it just me, or does this not work anymore in a SOA Suite PS5 install? (Or didn’t I pay attention in the older versions?
) The script <DOMAIN_HOME>/bin/setSOADomainEnv.sh reaves havoc regarding the USER_MEM_ARGS by simply overwriting it.
I was fed up with this, and hacked the setSOADomainEnv.sh. If you want the USER_MEM_ARGS to be the one and only memory setting, change the following:
Add in the beginning
if [ -n "${USER_MEM_ARGS}" ] ; then
SAVED_MEM_ARGS="${USER_MEM_ARGS}"
fi
to store any set USER_MEM_ARGS into a new variable SAVED_MEM_ARGS. Then the script will start doing all kinds of magic with all kind of settings.
Then add at the end, for example line 220 the following:
if [ -n "${SAVED_MEM_ARGS}" ] ; then
USER_MEM_ARGS="${SAVED_MEM_ARGS}"
fi
to restore the USER_MEM_ARGS.
Setting the Java memory arguments in OFM 11.1.1.6.0,


Whitehorses is specialized in succesfully implementing Oracle SOA solutions: BPEL, OSB, WebLogic & BPM
{ 3 comments… read them below or add one }
Looks like http://www.deltalounge.net/wpress/2011/09/memory-issues-after-installing-oer/
Indeed looks like the same issue. IMHO setSOADomainEnv.sh is just ..weird…
This is really a pian in 11.1.1.6