Composite instances showing up in a running state? Is there a way to solve?
Composite instances shows as running in em console if there is a fault in processing.
These composites are not actually running but they are dehydrated instances with soa auto recover enabled and this which SOA Auto recovery tries to recover these instances.
Ideally the component which happens to be in running state may actually have ended process due to fault, this can be checked drilling down to the faulted sub process and check for the error, the same can be checked in database in cube_instance table for fault states. We can safely abort these processes or delete them as permitted in your IT purging strategies.
Cubastion is among a very small number of specialized Siebel CRM Oracle Gold Partners in SME.