1. Developing SOA Applications with Oracle SOA Suite
  2. Advanced Topics
  3. Managing Large Documents and Large Numbers of Instances
  4. Best Practices for Handling Large Documents
  5. General Tuning Recommendations
  6. General Recommendations

General Recommendations

This section provides general tuning recommendations.

  • Increase the JTA transaction timeout to 500 seconds in Oracle WebLogic Remote Console. For instructions, see section "Resolving Connection Timeouts" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.

  • In Oracle Enterprise Manager Fusion Middleware Control, set the audit level to Off or Production at the SOA composite application level. See Setting Audit Levels from for Large Payload Processing for additional information.

  • Uncomment the following line in setDomainEnv.sh (for Linux) or setDomainEnv.bat (for Windows) for JAVA_OPTIONS, and restart the server. If this line does not exist, add it. Without this setting, large payload scenarios fail with a ResourceDisabledException error for the dehydration data source. 

    -Dweblogic.resourcepool.max_test_wait_secs=30

  • Update the heap size in setSOADomainEnv.sh or setDomainEnv.bat as follows: 

    DEFAULT_MEM_ARGS="-Xms1024m -Xmx2048m"

  • Use optimized translation functions, which are available while performing transformations and translations of large payloads (for example, ora:doTranslateFromNative, ora:doTranslateToNative, ora:doStreamingTranslate, and so on).

    For information about these functions, see XPath Extension Functions.

  • Extend data files for handling large attachments.

  • Increase the HTTP POST timeout for SocketException: Broken pipe errors in Oracle WebLogic Remote Console. See Increasing the HTTP POST Timeout

  • If you are processing large documents and run into timeout errors, perform the following tasks:

    • Increase the timeout property value.

    • Increase the Stuck Thread Max Time property value.

    For more information, see Increasing the Timeout Value.