Sunday, October 2, 2011

Disabling keepAlives in Oracle SOA Suite

Problem:

The target service or application (external to SOA Suite) is receiving a large number of connections from SOA Suite.


Solution:

1. For SOA Suite 10g, edit opmn.xml and add the highlighted argument to the OC4J_SOA startup parameters. For example:
<data id="java-options" value="-Xmx2048m -Xms2048m -XX:MaxPermSize=512M -Djava.security.policy=$ORACLE_HOME/j2ee/oc4j_soa/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false -Doc4j.userThreads=true -Doracle.mdb.fastUndeploy=60 -Doc4j.formauth.redirect=true -Djava.net.preferIPv4Stack=true -Dorabpel.home=/u01/app/oracle/OracleAS_1/bpel -Xbootclasspath^/p:/u01/app/oracle/OracleAS_1/bpel/lib/orabpel-boot.jar -Doracle.security.jazn.config=/u01/app/oracle/OracleAS_1/j2ee/oc4j_soa/config/jazn.xml -Doraesb.home=/u01/app/oracle/OracleAS_1/integration/esb -Daia.home=/u01/app/oracle/aia_1 -Dhttp.proxySet=false -Xgcpolicy:subpool -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xverbosegclog:/u01/app/oracle/OracleAS_1/opmn/logs/gc_oc4j_soa.log -DHTTPClient.disableKeepAlives=true"/>
2. For SOA Suite 11g, edit setSOADomainEnv.sh and add the highlighted argument to the soa_server1 startup parameters. For example:
PORT_MEM_ARGS="-Xms6144m -Xmx6144m -Xgcprio:throughput -XX:+HeapDumpOnOutOfMemoryError -XXtlasize=min=16k,preferred=128k,wasteLimit=8k -XX:+UseCallProfiling -DHTTPClient.disableKeepAlives=true"

Applicable Versions:
  • Oracle SOA Suite 10g (running on Oracle Application Server 10g)
  • Oracle SOA Suite 11g (running on Oracle WebLogic Server 11g)

Ahmed Aboulnaga

No comments: