BPM Process Startup Failes With Default configuration is not defined in file "workflow-identity-config.xml" (Doc ID 2252298.1)

Last updated on JUNE 08, 2017

Applies to:

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

Symptoms

After starting SOA server, if multiple BPM processes startup at same time, one process fails with following error.

[2017-03-02T10:37:47.066-06:00] [AdminServer] [ERROR] [] [oracle.bpm.system]
[tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: <anonymous>] [ecid:
e4809544-89ab-43fe-ae84-6f4c3b6ad197-000000df,1:26946] [APP: soa-infra]
[oracle.soa.tracking.FlowId: 240014] [oracle.soa.tracking.InstanceId: 270027]
[oracle.soa.tracking.SCAEntityId: 210002] [oracle.soa.tracking.FaultId:
50001] [FlowId: 0000LeFsaX21VcWFLzvH8A1Oi4Ng00000G] cube deliveryError not
handled.[[
failure to handle a error thrown from a scope, by any blocks in the scope
chain.
This exception occurred because the error thrown in the BPMN flow was not
handled by any error handlers and reached the top-level scope.
A top-level error handler should be added to the flow to handle errors not
caught from within the flow.
, Cikey=270027, FlowId=240014, Current Activity
Key=270027-EVT17689166293833-Simpletask.1-1, Current Activity Label=Start,
InvokeMessageGuid=8f8b58e3-ff66-11e6-a9d4-000c2920a59b,
ComponentDN=default/simpletask!1.0*soa_2731fa72-e91b-47a0-a837-35ba839c9ca5/Si
mpletask ORABPEL-10577
.
Default configuration is not defined.
Default configuration is not defined in configuration file
"workflow-identity-config.xml".
Specify default configuration in the file "workflow-identity-config.xml".
Irrespective of the number of configurations, one should always be marked as
default. Contact Oracle Support Services if error is not fixable.
.
at
oracle.tip.pc.services.identity.config.ISConfiguration.getConfigurationInstance(ISConfiguration.java:241)
at
oracle.tip.pc.services.common.ServiceFactory.getAuthorizationServiceInstance(ServiceFactory.java:113)
at
oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.getParticipantsForProcessRole(DeploymentDescriptorUtil.java:160)
at
oracle.bpm.bpmn.engine.model.runtime.util.BPMNUtility.getProcessInstance(BPMNUtility.java:727)
at
oracle.bpm.bpmn.engine.model.runtime.util.BPMNUtility.insertInstance2Track(BPMNUtility.java:662)
at
oracle.bpm.bpmn.engine.model.runtime.util.BPMNUtility.insertInstance2Track(BPMNUtility.java:158)
at
oracle.bpm.bpmn.engine.model.runtime.microinstructions.MIInsertInstance2Track.insertInstance2Track(MIInsertInstance2Track.java:80)
at
oracle.bpm.bpmn.engine.model.runtime.microinstructions.MIInsertInstance2Track.doExecute(MIInsertInstance2Track.java:67)
at oracle.bpm.bpmn.engine.microkernel.MIBase.execute(MIBase.java:34)
...

 The problem happens even if workflow-identity-config.xml is correct. And the problem occurs only once until SOA server restart.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms