Unexpected behaviour on receive

[gv...@intec.ugent.be]

Hello,

First of all I would like to apologize if this is not the correct channel
to post this issue. The issue regards unexpected behaviour, at least it is
not what I expected, concerning correlation.

I created a rather straightforward BPEL process with several receives.
These receives are evidently correlation using the mechanisms provided by
WS-BPEL. Everything works well if I launch several instances using
different correlation data. When I consecutively invoke the first receive
(which of course has the createInstance attribute set to "yes") with the
same correlation data I expected to only see one of these invocations to
result in a new process instance. However, to my surprise, all invocations
resulted in a newly instantiated process. This caused my engine to get in
an inconsistent state. The invocations to the next receives were rather
arbitrary allocated to process instances. Of course the engine does not
know what to do, when it is allowed to have multiple distinct process
instances with the same correlation data.
What I hoped to see was that the first invocation got through and all the
others returned a fault message.

Can someone attend to this or point me out were I can rectify this for my
usage erroneous behaviour in the code?

Thanks in advance,
Gregory