[ODE-974] On process versioning, instances of retired version are not picking the data from BPEL_UNMATCHED

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.3.7, 1.4
• Component/s: BPEL Runtime
• Assignee: Sathwik
• Reporter: Jayant Vaish
• Created: 11/Oct/12 08:53
• Updated: 28/Nov/17 07:56
• Resolved: 08/Jul/16 07:13

Description

If there is a process which receives the data from another process in such a manner that the data arrives first and then the instance reaches the activity which needs it, the instance picks the data from the BPEL_UNMATCHED table.
If we deploy the process again, then the running instances of retired process are not picking data from BPEL_UNMATCHED hence not getting completed.

I have attached the process. Here are the steps to reproduce :

1. Deploy the process. Start the parent process from console.
2. Deploy again.
3. After one min you will see that the child process has completed, and there is an entry in BPEL_UNMATCHED.
4. After two mins you will see that parent process is still waiting for the message from child process, which has already came and currently is in BPEL_UNMATCHED table.

Issue Links

• is required by: ODE-1061 List of Bugs to be ported to trunk from 1.3.7
• requires: ODE-829 if process is retired the inflight instances dont work