[
https://issues.apache.org/jira/browse/CXF-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519296#comment-14519296
]
Akitoshi Yoshida commented on CXF-6323:
---------------------------------------
One option currently frequently used is to activate the robust mode (setting
context property org.apache.cxf.oneway.robust to true at the service endpoint).
This makes sure that the retry will always occur from the client because the
ack will only be returned to the client when the service call succeeds.
> WS-RM redelivery not implemented
> --------------------------------
>
> Key: CXF-6323
> URL: https://issues.apache.org/jira/browse/CXF-6323
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.7.14, 3.0.4
> Reporter: Jochen Riedlinger
>
> We build an application based on CXF using WS-RM.
> Since we have/had some issues I tried with 2.7.14 and 3.0.4.
> After the baisc things worked we tested the reliability of the WS-RM
> implementation and crashed the application after the message was put in the
> store.
> I expected that the application-server tries to redeliver the message after
> restart. Unfortunately that never happens.
> Debugging the problem and taking a look into the source code I found that
> code (in org.apache.cxf.ws.rm.RMManager):
> {code:java}
> private void reconverDestinationSequence(Endpoint endpoint, Conduit conduit,
> Destination d,
> DestinationSequence ds) {
> d.addSequence(ds, false);
> //TODO add the redelivery code
> }
> {code}
> It would be nice if someone could correct/implement this;-)
> Befor that you the WS-RM implementation is not reliable.;-)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
