Thursday, March 27, 2014

Solving Oracle BPM 11g Composite Error - Could not locate composite. Runtime Operation Error

When you've worked on many BPM composites, deploying and undeploying it over and over, someway, you could encounter this following error in the log.

<Mar 20, 2014 11:03:30 AM WIT> <Error> <oracle.soa.services.workflow.task> <BEA-000000> <<.> Could not locate composite.
Could not locate composite for workflow component default/PROJECTNAME!1.3.1*soa_1d2b1813-58f0-4264-8581-85013cd8eaba/CompositeName.
Ensure composite has been successfully deployed, and that the SOA server has completed loading composites.

ORABPEL-30084

Could not locate composite.
Could not locate composite for workflow component default/PROJECTNAME!1.3.1*soa_1d2b1813-58f0-4264-8581-85013cd8eaba/CompositeName.

Ensure composite has been successfully deployed, and that the SOA server has completed loading composites.

When you check on Enterprise Manager console (http://host:port/em), the composite is already undeployed but the workspace is still trying to find it, thus producing the following error possibilities in the BPM workspace (http://host:port/bpm/workspace):

"Runtime Operation Error"
"Could not perform the batch operation"

This thing can impact many things, starting from simple thing like user annoyance and also major thing like unaccessible Process Tracking and altering due to Runtime Operation Error.

Annoying as it is, but the solution is very simple.

Use your DB browser and access SOAINFRA schema. There, open WFTASKMETADATA table and delete any unused composite that prompt the error on the log.

Restart your MS, then try to access BPM workspace. The error will be no more.
Hope it helps!


1 comment:

  1. This suggestion worked perfectly. Although, it wasn't necessary to restart the managed server after deleting from dev_soainfra.wftaskmetadata table. Note: wls version 12.1.3/ db v. 12.1.2.0.

    ReplyDelete