Troubleshoot Integration Activations
Learn about troubleshooting integration activations in Oracle Integration.
Troubleshoot Integration Activations
If your integration fails to activate, review the following failure issues and corrective actions.
Activation Failure Causes | Corrective Actions |
---|---|
WSDL issues:
|
|
Deployment timeout issues. |
Retry the activation because the server may be slow to react. |
Database issues:
|
|
A connection is down or was modified. |
|
Managed server unavailable. |
|
If an integration contains too many actions (for example, it has 25 or more stage
write actions), activation failure can
occur:
|
Optimize the integration. For example, split the integration into multiple integrations. |
Delay in Message Processing of First Instance after Activation
After activation of an integration, there is a several second delay between when the instance is created and when the message is processed. This is the expected behavior.
On the first request for all integrations, the artifacts and back-end processes are lazy loaded as a first step. This can make for a longer time period spent between the first two steps shown in the activity stream when compared to subsequent invocations. This is the expected behavior for the initial request, and by design.
Sep 3rd 12:43:16.442 PM UTC 2020 Message received: Instance create
Sep 3rd 12:43:23 Message processed by Trigger
Note the seven second delay between when the message was received and processed.