[
https://issues.apache.org/jira/browse/ODE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468625#comment-13468625
]
Gary Brown commented on ODE-939:
--------------------------------
The problem appears to be in the
BpelRuntimeContextImpl.completeOutstandingMessageExchanges() method. The method
you refer to is only called within the terminate activity.
For the simple example attached, the mex.getStatus() is returning ASYNC, which
results in the status being set to COMPLETED_OK.
If it was either REQUEST or not ASYNC or RESPONSE, then it would result in a
fault - although the OConstants.qnMissingReply fault name is not actually used.
Not sure under what situations these various cases get called. Just wondering
whether the logic could be changed to be:
for each outstanding mex {
if pattern == RequestResponse {
if response and faultResponse are both null {
return missingReply fault
}
}
}
> Fault missingReply is not thrown
> --------------------------------
>
> Key: ODE-939
> URL: https://issues.apache.org/jira/browse/ODE-939
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.5
> Reporter: Gary Brown
> Attachments: hwnoreply.zip
>
>
> According to the BPEL spec, the 'missingReply' fault should be: "Thrown when
> an inbound message activity has been executed, and the process instance or
> scope instance reaches the end of its execution without a corresponding
> <reply> activity having been executed."
> The attached is a simple hello world example with a missing reply. The
> process instance reaches the end, but does not throw the fault, and instead
> the client (e.g. soapui) simply times out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
