oracle soa tunning tips

Resolving Connection Timeouts

You can receive a connection timeout error under circumstances such as the following:

• You run a SOA composite application with a large payload that takes more than 30 seconds to process.
• You are invoking a stress test using a large payload from the Test Web Service page of Oracle Enterprise Manager Fusion Middleware Control Console.
• You are passing a large number of message files (one million) into a composite with a file adapter service.
• You are retrieving instance and fault count metrics in Oracle Enterprise Manager Fusion Middleware Control Console.

To avoid receiving timeout errors, increase the transaction timeout property as follows:

1. Log into Oracle WebLogic Administration Console.
2. Click JTA.
3. Change the value of Timeout Seconds (the default is 30).
4. Click Save.
5. Restart Oracle WebLogic Server.

B.6 Increasing Database Connection Values

You can receive the following error message because of slow connections to the database.

Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.1.0) (Build 
090304)): oracle.toplink.exceptions.DatabaseException 
Internal Exception: java.sql.SQLException: Internal error: Cannot obtain 
XAConnection weblogic.common.resourcepool.ResourceDeadException: Pool 
SOADataSource has been disabled because of hanging connection tests, cannot 
allocate resources to applications.

If this occurs, perform the following steps:

1. Open the DOMAIN_HOME\bin\setSOADomainEnv.cmd file.
2. Uncomment the lines shown in bold.
   

   # 8331492: Value of weblogic.resourcepool.max_test_wait_secs is 10 
   # seconds. It can be increased by uncommenting line below if your database 
   # connections are slow. See SOA documentation for more details. 
    EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES}
   -Dweblogic.resourcepool.max_test_wait_secs=30" 
   export EXTRA_JAVA_PROPERTIES