My Oracle Support Banner

BPM/SOA composite deployment fails on a clustered environment with, 'FabricException: Timed out waiting for operation to complete' (Doc ID 2208452.1)

Last updated on JANUARY 08, 2024

Applies to:

Oracle Business Process Management Suite - Version 12.2.1.0.0 to 12.2.1.1.0 [Release 12c]
Oracle SOA Suite - Version 12.2.1.0.0 to 12.2.1.0.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

When the first BPM/SOA managed server to be started in a cluster is restarted, the composite deployment fails with the below error:

Start Order: Admin -> server1 -> server2, then restart server1

 

####<May 17, 2016 6:36:23 PM JST> <Error> <ServletContext-/soa-infra>
<myhost> <soa_server1> <[STUCK] ExecuteThread: '5' for queue:
'weblogic.kernel.Default (self-tuning)'> <weblogic> <>
<30eb6904-1278-4030-b73e-6ec6cf48d8f0-000000f8> <1463477783568>
<[severity-value: 8] [rid: 0:7:2] [partition-id: 0] [partition-name: DOMAIN]
> <BEA-000000> <Error during deployment
oracle.fabric.common.FabricException: Timed out waiting for operation to complete.
at
oracle.integration.platform.blocks.deploy.CompositeDeploymentCoordinatorMessages.throwTimedOutWaiting(CompositeDeploymentCoordinatorMessages.java:151)
at
oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.submitRequestAndWaitForCompletion(CoherenceCompositeDeploymentCoordinatorImpl.java:651)
at
oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.submitRequestAndWaitForCompletion(CoherenceCompositeDeploymentCoordinatorImpl.java:604)
at
oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(CoherenceCompositeDeploymentCoordinatorImpl.java:309)
at
oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(CoherenceCompositeDeploymentCoordinatorImpl.java:279)
at
oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:614)
at
oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:369)
at
oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:184)
at
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:493)
at
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:382)
at
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:191)
at
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:142)
at
oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:217)
at
oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:142)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.