[
https://issues.apache.org/jira/browse/ODE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606093#action_12606093
]
Rafal Rusin commented on ODE-304:
---------------------------------
I think I found a workaround for it (which seems to be not supported by BPEL
too).
One may add an additional Pick on service eg. 'cancel' and throw user error
eg. 'TERMINATED' when a message comes in. After throwing an exception, picks
seem to dispose acquired correlation id.
> Pick not unregistered after manual process termination
> ------------------------------------------------------
>
> Key: ODE-304
> URL: https://issues.apache.org/jira/browse/ODE-304
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.1.1
> Environment: J2EE war ODE 1.1.1, JBI ODE 1.2
> Reporter: Rafal Rusin
>
> I've got a following process (simplified):
> 1.<receive correlation=cid createInstance="yes"/>
> 2.<pick correlation=cid/>
> I send a message with cid=100, process goes to 2. and I run terminate from
> management API.
> Then I send again message with cid=100 to it and it hangs with no response.
> It seems like a correlation 100 is still assigned to a terminated process
> instead of being released. So the message goes to a terminated process.
> Regards
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
