Recovering from BPMN Process Service Engine Faults

Troubleshooting Oracle SOA Suite B-5 hard nofile 4096 4. Close your terminal and reopen for the change to take effect. A system restart is not required. B.5 Extending Tablespaces to Avoid Problems at Runtime If the database tablespace is not extended, runtime processing can be impacted. Messages are not processed or persisted, and exception errors similar to the following can appear in the log files. This is because Oracle BPEL Process Manager relies on the database to store instance data. If the database is not available, runtime processing is impacted. INFO: MediatorServiceEngine returning after processing the request for operation = processResponse [EL Warning]: 2009.01.14 11:46:16.783--UnitOfWork32372128--Exception [EclipseLink-4002] Eclipse Persistence Services - 1.1 Build SNAPSHOT-20081007: org.eclipse.persistence.exceptions.DatabaseException Internal Exception: java.sql.BatchUpdateException: ORA-01691: unable to extend lob segment SH_SOAINFRA.SYS_LOB0000145067C00007 by 1024 in tablespace SH_SOAINFRA Error Code: 1691 Query: InsertObjectQuerycom.collaxa.cube.persistence.dto.AuditTrail199b33d [EL Warning]: 2009.01.14 11:46:16.782--UnitOfWork32372128--Exception [EclipseLink-4002] Eclipse Persistence Services - 1.1 Build SNAPSHOT-20081007: org.eclipse.persistence.exceptions.DatabaseException Internal Exception: java.sql.BatchUpdateException: ORA-01691: unable to extend lob segment SH_SOAINFRA.SYS_LOB0000145067C00007 by 1024 in tablespace SH_SOAINFRA . . . . . . Ensure that you set a tablespace to automatically extend itself by a specified amount when it reaches its size limit. If you do not enable autoextend, ensure that you respond when alerted that the tablespace is reaching its critical or warning threshold size. You can respond to size alerts by manually increasing the tablespace size. B.6 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. ■ 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. To avoid receiving timeout errors, increase the transaction timeout property as follows: 1. Log into Oracle WebLogic Administration Console. B-6 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite

2. Click JTA.

3. Change the value of Timeout Seconds the default is 30.

4. Click Save.

5. Restart Oracle WebLogic Server. B.7 Updating the EJB Transaction Timeout Value in the Deployment Archive After SOA Infrastructure Failure Updating the transaction time out value for the FacadeFinderBean property in Oracle WebLogic Server Administration Console under Deployments expanded SOA Infrastructure Application FacadeFinderBean Configuration tab can result in the following error after restarting the SOA Infrastructure: java.lang.IllegalArgumentException: Cannot convert value of type [Proxy223 implementing oracle.bpel.services.workflow.verification.IVerificationService,org.springframe work.aop.SpringProxy,org.springframework.aop.framework.Advised] to required type [oracle.bpel.services.workflow.verification.IVerificationService] for property verificationService: no matching editors or conversion strategy found Message icon - Warning Errors were encountered while performing this operation. The SOA Infrastructure status is also displayed as failed. This error is not specific to FacadeFinderBean; it also applies to any EJB that is part of the SOA Infrastructure application. To resolve this error, you must manually modify the transaction timeout setting in your deployment archive. To update the transaction timeout setting: 1. Open the fabric-ejb.jar file in your deployment archive. 2. Increase the transaction timeout value in the META-INFweblogic-ejb-jar.xml file to a larger value. 3. Rejar the file. 4. Restart the managed server that includes the SOA Infrastructure by following the instructions in Section 3.2, Stopping and Starting the Managed Server and SOA Infrastructure. B.8 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 Note: This issue may also occur while updating any EJBs deployed as part of the SOA Infrastructure application. If this issue occurs, you must update the corresponding contained JAR file for those EJBs in a similar fashion. Troubleshooting Oracle SOA Suite B-7 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 3. Save your changes and restart the managed Oracle WebLogic Server. B.9 Resolving MaxMessageSizeExceededException Errors Caused By Large Payloads If you provide a large payload for example, 12 MB to your deployed SOA composite application, then click View XML Document in the audit trail to view the payload, you can encounter MaxMessageSizeExceededException errors. This error can be resolved by setting the following JVM parameter. 1. Open the following file: ■ On UNIX operating systems, open MIDDLEWARE_HOMEuser_ projectsdomainsdomain_namebinsetDomainEnv.sh. ■ On Window operating systems, open MIDDLEWARE_HOME\user_ projects\domains\domain_name\bin\setDomainEnv.bat. 2. Add the weblogic.MaxMessageSize property with the following value: EXTRA_JAVA_PROPERTIES={EXTRA_JAVA_PROPERTIES} -Dweblogic.MaxMessageSize=20000000 export EXTRA_JAVA_PROPERTIES 3. Restart the server. B.10 Accessing Oracle Enterprise Manager Fusion Middleware Control on Dual Stack Hosts that Support IPv4 and IPv6 If you run Oracle SOA Suite on a dual stack host that supports both IPv4 and IPv6, you must update the etchosts file as shown in Table B–1 for IPv4 clients to access IPv6 URLs in Oracle Enterprise Manager Fusion Middleware Control. Table B–1 IPv4 and IPv6 Settings in etchosts File On The... Edit the etchosts File as Follows.... On the IPv4 client: xx .xxx.xxx.xxx myhost10-ipv6 where xx.xxx.xxx.xxx is the IP address of IPv6. On the IPv6 client fdf5:74cc:db0a::0:1 myhost10-ipv6 myhost10-ipv6.us.oracle.com Note : Replace fdf5:74cc:db0a::0:1 with a value appropriate to your host environment.