Recovering from BPMN Process Service Component Faults

B Troubleshooting Oracle SOA Suite B-1 B Troubleshooting Oracle SOA Suite This appendix describes how to troubleshoot issues you can encounter when using Oracle SOA Suite. This appendix includes the following topics: ■ Section B.1, Best Practice for Starting and Stopping a Managed Server ■ Section B.2, Specifying the Proxy Server ■ Section B.3, Optimizing the Loading of Pages with Instance and Fault Metrics ■ Section B.4, Resolving Message Failure Caused by Too Many Open Files ■ Section B.5, Extending Tablespaces to Avoid Problems at Runtime ■ Section B.6, Resolving Connection Timeouts ■ Section B.7, Updating the EJB Transaction Timeout Value in the Deployment Archive After SOA Infrastructure Failure ■ Section B.8, Increasing Database Connection Values ■ Section B.9, Resolving MaxMessageSizeExceededException Errors Caused By Large Payloads ■ Section B.10, Accessing Oracle Enterprise Manager Fusion Middleware Control on Dual Stack Hosts that Support IPv4 and IPv6 ■ Section B.11, Limitation on Using the Safari Browser to View WSDL File Content ■ Section B.12, Flow Diagram Does Not Display The First Time on Some Lower End Hosts ■ Section B.13, Setting Logging Levels for Troubleshooting ■ Section B.14, Human Workflow Troubleshooting B.1 Best Practice for Starting and Stopping a Managed Server As a best practice, it is always recommended that you start and stop a managed server through one, but not both, of the following methods. Do not mix these methods, such as starting the managed server from the command line and stopping it from Oracle Enterprise Manager Fusion Middleware Control, or vice versa. ■ Oracle Enterprise Manager Fusion Middleware Control With this method, the node manager must be up and running. The node manager tracks all managed server startups and shutdowns performed from Oracle Enterprise Manager Fusion Middleware Control. With this method, the server state is not an issue. B-2 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite ■ Command line With this method, the node manager does not track the server state. Therefore, if you start the server from the command line and shut it down from Oracle Enterprise Manager Fusion Middleware Control, the Oracle WebLogic Administration Server accesses the node manager to determine its status, which returns a state of Unknown. Perform the following steps to stop and start the server from Oracle Enterprise Manager Fusion Middleware Control. 1. Expand the WebLogic domain. 2. Select the managed server for example, named soa_server1.

3. Select Control Shut Down.

4. Select Control Start Up.

For information on starting and stopping managed servers from the command line, see Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite. B.2 Specifying the Proxy Server To use system properties to specify the proxy server, write your client application in the standard way, and then specify Java system properties when you execute the client application. setenv PROXY_SETTINGS -DproxySet=true -Dhttp.proxyHost=www-myproxy.us.mycompany.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|.us.mycompany.com |0:0:0:0:0:0:0:1|fe80:0:0:0:250:56ff:fe31 B.3 Optimizing the Loading of Pages with Instance and Fault Metrics Since production systems can include numerous composite instances and faults, there is a possibility of time-outs in the SOA Oracle Enterprise Manager Fusion Middleware Control pages as information retrieval becomes relatively slow. To optimize the loading performance of pages, you can enable a property setting in the SOA Infrastructure Common Properties page that disables the loading of all metrics information upon page load. The instances and faults metrics can be obtained on demand from the server.

1. In the navigator, click soa-infra.

2. Note that values appear in the Running and Total fields in the Recent Composite

Instances section and the Instances column of the Deployed Composites section. When these values are large, it can take time to load this page and other pages with similar information. Note: When you specify values for proxy properties such as http.proxyHost and http.proxyPort, also specify the http.nonProxyHosts property. Troubleshooting Oracle SOA Suite B-3

3. From the SOA Infrastructure menu, select SOA Administration Common

Properties .

4. In the Display Data Counts section, select the Disable fetching of instance and

fault count metrics checkbox.

5. Click Apply.

6. Return to the Dashboard page of the SOA Infrastructure. 7. Note that the values that previously displayed have been replaced with links. 8. Click a link. The values are calculated for the link you selected. When the calculation is complete, a message displays the total values. For more information about setting this property, see Section 3.1, Configuring SOA Infrastructure Properties.