Hi,

Consider the following BPEL process.

[Receives a request  -> Sends a request to a 'third-party-service' ->
Receives the response from the 'third-party-service' -> Sends the reply (to
a different destination)]

If there is a system failure when the ODE is waiting for the response from
the 'third-party-service', is there a way to correlate the request to
'third-party-service' sent before the system crash and request sent (due to
persistence) to the 'third-party-service' after system recovery? It seems
that the MessageExchangeIDs used in both occasions are different. Is there
some other property that can be used ?

Motive: If there is a way to identify that both requests are related to to
the same persisted job, one can filter such duplications and prevent
unnecessary invocations of the 'third-party-service' provided that response
of the first request to the 'third-party-service' is available by some
reliable transportation mechanism.

Any help, suggestions are appreciated !!

Sanka

Reply via email to