[
https://issues.apache.org/jira/browse/ODE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205320#comment-13205320
]
Tammo van Lessen edited comment on ODE-954 at 2/10/12 9:53 AM:
---------------------------------------------------------------
This is actually the expected behaviour. The BPEL spec is rather vague in this
regard and so ODE is it, too. BPEL 2.0 defines some constraints about the
uniqueness of correlation keys within a process instance but not across
multiple instances. So it is up to the modeller to define correlation sets in a
way that guarantees unique correlation during runtime. It's like in real life:
When you did a hotel reservation for a very common name, the room is assigned
to the first person with that name that shows up -- which may look like a
random assignment for others.
was (Author: vanto):
This is actually the expected behaviour. The BPEL spec is rather vague in
this regard and so ODE is it, too. BPEL 2.0 defines some constraints about the
uniqueness of correlation keys within a process instance but not across
multiple instances. So it is up to the modeller to define correlation sets in a
way that guarantees unique correlation during runtime.
> Should it be possible to have multiple instances with the same correlation
> key active simultaneously?
> -----------------------------------------------------------------------------------------------------
>
> Key: ODE-954
> URL: https://issues.apache.org/jira/browse/ODE-954
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.5
> Reporter: Gregory Van Seghbroeck
> Assignee: Tammo van Lessen
>
> At runtime it seems possible to create multiple process instances using the
> same correlation key. This evidently leads to correlation mismatches when the
> followup receives need to be matched, since it does not have a unique
> correlation key to tie an incomming message to a single process instance. The
> way the actual instances is "allocated" seems to happen quasi random.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
