[
https://issues.apache.org/jira/browse/ODE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606344#action_12606344
]
Rafal Rusin commented on ODE-304:
---------------------------------
Could you point me to a documentation, where this behaviour with terminated
instances and picks is specified? I read
http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.pdf
and googled about it and I didn't find information.
In wsbpel.pdf there in only written that every activity must be immediately
ended without processing handlers.
I agree with Alex that this has a business legitimation with retries.
I think that the terminated process shouldn't behave like suspended forever,
but rather like abnormally terminated, similarly to failing by <throw>, but
without processing handlers.
Regards
> 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.
