Details
-
Bug
-
Resolution: Done
-
Major
-
2.3.4.Final, 3.0.0.M2
-
None
Description
The structure of process:
<sequence>
<pick>
<receive>
</sequence>
Messages for <receive> and <pick> has to have same correlation IDs.
If we send message for <receive>, the riftsaw remember the message and after we send a message for <pick>, the process is completely performed.
I think this approach is right but the issue is that the riftsaw remember the message forever and if I send the message for <pick> once again with the same correlation ID, the process is completely performed without any needs of message for <receive> activity.
Attachments
Issue Links
- is related to
-
RIFTSAW-504 Sending messages in reverse order causes deadlock
- Open