"Internal error" message after clicking Application link in BPM Workspace and "Could not locate composite" error in the logs
(Doc ID 2305378.1)
Last updated on MAY 31, 2018
Applies to:
Oracle Business Process Management Suite - Version 12.1.3.0.0 and laterInformation in this document applies to any platform.
Symptoms
After logging into the BPM workspace and clicking the Applications link you receive an error:
"An internal error has occurred. Please contact the administrator or Oracle support to help"
You might also find the following exception in the server logs:
<May 8, 2018, 8:15:24,906 PM IST> <Error> <oracle.bpm.services.processMetadata> <BEA-000000> <Exception
exception.70805.type: error
exception.70805.severity: 2
exception.70805.name: Error while querying for initiatable processes for a given BPMContext
exception.70805.description: Error while querying for initiatable processes for a given BPMContext
exception.70805.fix: Error while querying for initiatable processes for a given BPMContext. Contact Oracle support if exception can not be fixed
ORABPEL-30084
exception.code:30084
exception.type: ERROR
exception.severity: 2
exception.name: Could not locate composite.
exception.description: Could not locate composite for workflow component default/<ProjectName>!<version>*soa_0926baaf-620d-4602-be9c-c97d956278d0/Initiator.
exception.fix: Ensure composite has been successfully deployed, and that the SOA server has completed loading composites.
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:287)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:532)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:313)
at oracle.bpel.services.workflow.metadata.ejb.TaskMetadataServiceBean_kykm8_EOImpl_12211_WLStub.getTaskDefinitionById(Unknown Source)
at oracle.bpel.services.workflow.metadata.client.TaskMetadataServiceRemoteClient.getTaskDefinitionById(TaskMetadataServiceRemoteClient.java:43)
at oracle.bpel.services.workflow.metadata.client.TaskMetadataServiceRemoteClient.getTaskDefinitionById(TaskMetadataServiceRemoteClient.java:65)
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 oracle.bpel.services.workflow.client.WFClientRetryInvocationHandler.invokeTarget(WFClientRetryInvocationHandler.java:141)
at oracle.bpel.services.workflow.client.WFClientRetryInvocationHandler.invoke(WFClientRetryInvocationHandler.java:80)
at com.sun.proxy.$Proxy689.getTaskDefinitionById(Unknown Source)
at oracle.bpm.services.processmetadata.impl.ProcessMetadataService.getInitiatableProcesses(ProcessMetadataService.java:666)
...
exception.70805.type: error
exception.70805.severity: 2
exception.70805.name: Error while querying for initiatable processes for a given BPMContext
exception.70805.description: Error while querying for initiatable processes for a given BPMContext
exception.70805.fix: Error while querying for initiatable processes for a given BPMContext. Contact Oracle support if exception can not be fixed
ORABPEL-30084
exception.code:30084
exception.type: ERROR
exception.severity: 2
exception.name: Could not locate composite.
exception.description: Could not locate composite for workflow component default/<ProjectName>!<version>*soa_0926baaf-620d-4602-be9c-c97d956278d0/Initiator.
exception.fix: Ensure composite has been successfully deployed, and that the SOA server has completed loading composites.
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:287)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:532)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:313)
at oracle.bpel.services.workflow.metadata.ejb.TaskMetadataServiceBean_kykm8_EOImpl_12211_WLStub.getTaskDefinitionById(Unknown Source)
at oracle.bpel.services.workflow.metadata.client.TaskMetadataServiceRemoteClient.getTaskDefinitionById(TaskMetadataServiceRemoteClient.java:43)
at oracle.bpel.services.workflow.metadata.client.TaskMetadataServiceRemoteClient.getTaskDefinitionById(TaskMetadataServiceRemoteClient.java:65)
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 oracle.bpel.services.workflow.client.WFClientRetryInvocationHandler.invokeTarget(WFClientRetryInvocationHandler.java:141)
at oracle.bpel.services.workflow.client.WFClientRetryInvocationHandler.invoke(WFClientRetryInvocationHandler.java:80)
at com.sun.proxy.$Proxy689.getTaskDefinitionById(Unknown Source)
at oracle.bpm.services.processmetadata.impl.ProcessMetadataService.getInitiatableProcesses(ProcessMetadataService.java:666)
...
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 |