Tasks Throw an ORABPEL-02055 Error When Inserted Into an Open Schedule
(Doc ID 1478415.1)
Last updated on MAY 14, 2021
Applies to:Hyperion Financial Close Management - Version 184.108.40.206.000 and later
Information in this document applies to any platform.
When attempting to open a schedule consisting of several tasks, or when attempting to add a task to a previously open schedule, the following error occurs:
[2012-06-01T15:38:56.773-05:00] [soa_server1] [ERROR]  [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-19] [userId: <user1>] [ecid: <ecid>] [APP: soa-infra] [composite_name: FCCNotificationComposite] [component_name: TriggerNotification] [component_instance_id: C89944F1AC2911E1BFC9E5F83E346219] [composite_instance_id: 130067] Failed to handle dispatch message ... exception ORABPEL-05002[[
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Exception not handled by the Collaxa Cube system.
an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: "java.security.PrivilegedActionException: ORABPEL-02055
Fault not handled.
failure to handle a fault thrown from a scope, by any blocks in the scope chain.
This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.
A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
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