This section is not about troubleshooting SOA composite instance failures, but rather about troubleshooting composite instances in general. Just because a composite is not reported as failed does not mean it does not warrant investigation. For example, it is entirely possible that when dealing with asynchronous services, there might be synchronization issues between concurrent threads that are trying to access a schema and the thread locking mechanism being unable to avoid deadlocks. This would leave the transaction in a pending state and not faulted. This behavior may require further investigation.

Chapter 6, Monitoring Oracle SOA Suite 12c, described in detail how to administer and manage faults. Faulted instances, in a way, are easier to deal with than non-faulted instances, as at least you have an error to begin with. Refer to this chapter to understand how to recover faults manually, automatically, and in bulk.

In the section titled Identifying...