Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
steps to reproduce
1. deploy version of process with two receives
2. create instance by sending message for first receive, but not complete instance
3. deploy newer version of the process with partnerlink removed/renamed
4. send second message for receive for the instance created in 2
we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
Instead BPELEngine should iterate over both the versions