Troubleshooting composite instances

This section is not about troubleshooting composite instance failures, but rather troubleshooting composite instances in general. Just because a composite is not reported as failed does not mean it does not warrant investigation. Take, for example, a scenario where there are asynchronous processes that are deployed to the service infrastructure. By their nature, whenever there is a dehydration point in the process, the threads running the process instances try to access the underlying database schemas for reading, retrieving, and writing instance information. In these cases, it is entirely possible that there might be synchronization issues between concurrent threads trying to access the database schema and, as such, the default server level thread locking mechanism could lead to a deadlock. This would leave the transaction in a pending state and not faulted. This behavior, though intermittent, may require further investigation.

Chapter 5, Configuring...