My Oracle Support Banner

The Composite Fails To Start With "BPEL 1.1 Compilation Failed" Error (Doc ID 2847610.1)

Last updated on MAY 15, 2023

Applies to:

Oracle SOA Suite - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

When a composite starts it fails with the following error:

oracle.fabric.common.FabricException: Error occurred during deployment of component: <Process name> to service engine: implementation.bpel, for composite: <Composite name>: ORABPEL-05215

Error while loading process.
The process domain is encountering the following errors while loading the process "<process name>" (composite "<Composite Name>!1.01*soa_b53a8e5e-cf81-4d49-9860-9f86eb1c0a9c"): BPEL 1.1 compilation failed.
This error contained an exception thrown by the underlying process loader module.
Check the exception trace in the log (with logging level set to debug mode). If there is a patch installed on the server, verify that the bpelcClasspath domain property includes the patch classes.

at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployComponents(CompositeDeploymentConnection.java:352)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:138)
at oracle.integration.platform.blocks.deploy.CompositeDeployerImpl.deploy(CompositeDeployerImpl.java:228)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:86)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:294)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:98)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
at com.sun.proxy.$Proxy525.deploy(Unknown Source)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$DeployedCompositeLoader.run(FabricKernelInitializerServlet.java:1408)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: ORABPEL-05215

Error while loading process.
The process domain is encountering the following errors while loading the process "<Composite name>" (composite "<Composite name>!1.01*soa_b53a8e5e-cf81-4d49-9860-9f86eb1c0a9c"): BPEL 1.1 compilation failed.
This error contained an exception thrown by the underlying process loader module.
Check the exception trace in the log (with logging level set to debug mode). If there is a patch installed on the server, verify that the bpelcClasspath domain property includes the patch classes.

at oracle.fabric.CubeServiceEngine.load(CubeServiceEngine.java:1333)
at oracle.fabric.CubeServiceEngine.load(CubeServiceEngine.java:221)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployComponents(CompositeDeploymentConnection.java:349)
... 22 more
Caused by: ORABPEL-05215

Changes

 The customer changed the host name where the composite runs.

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


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