Re: RMTxStore.getDestinationSequences is not recovering last processed messageId

[zzaili <zz...@hotmail.com>]

Yes, this happens to our application too. We are using cxf 2.7.17 for
providing the reliable messaging. When a client calls the service and no
results are returned in time the framework retransmits the request. But at
the time the server gets the retransmission the original request has been
already delivered and therefore the server side cxf framework sends the
following soap fault.

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Body><soap:Fault><soap:Code><soap:Value>soap:Receiver</soap:Value></soap:Code><soap:Reason><soap:Text
xml:lang="en">Message with number 1 in sequence
urn:uuid:402ec284-0c44-4cb9-ab87-0927fee8a59d has already been
delivered.</soap:Text></soap:Reason></soap:Fault></soap:Body></soap:Envelope>

But the client side fails to parse the soap fault because it does not have
action header and the expected Detail. I am not sure how to fix this to let
the client ignore this soap fault.




--
View this message in context: http://cxf.547215.n5.nabble.com/RMTxStore-getDestinationSequences-is-not-recovering-last-processed-messageId-tp5765307p5771847.html
Sent from the cxf-user mailing list archive at Nabble.com.