[ODE-972] Inovation failure within associated scope of onAlarm results in the process not continuing even after the successful retry

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 1.3.4, 1.3.5, 2.0
• Component/s: BPEL Runtime
• Labels: patch
• Assignee: Unassigned
• Reporter: Sathwik
• Created: 28/Sep/12 07:13
• Updated: 30/Oct/12 05:19

Description

This could be a regression from ODE-684

Problem statement:
There is an invoke activity within the onAlarm scope. If the external service is not available then this invoke fails and the process goes into a failure state. Once the external service is up and running, we can retry the activity which will succeed. But the problem now is that parent scope doesn't continue it's processing, and remains in InProgress state for ever.

Process Behaviour:

Testcase 1: Fire onEvent message after the 2 min Timer activity completes in parent scope

a) Initiate the process.
b) onAlarm goes into a failure state.
c) Wait for 2 minutes so that the timer in the parent scope executes followed by Task1.
d) Now fire the onEvent message from SoapUI. The message gets stored in BPEL_UNMATCHED.
e) Start the mock service in SOAPUI.
f) Retry the invoke activity that has failed inside onAlarm. It completes successfully.
g) The process remains in progress state.

Testcase 2: Fire onEvent message Before the 2 min Timer activity completes in parent scope

a) Initiate the process.
b) onAlarm goes into a failure state.
c) Now fire the onEvent message from SoapUI. The message gets routed successfully.
d) The process remains in progress state.