[
https://issues.apache.org/jira/browse/CXF-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518940#comment-14518940
]
Jim Ma commented on CXF-6323:
-----------------------------
It seems that recover DestinationSequence won't help much ack message delivery.
When the server restarts, the connection previously established with client
will be droped . There is no way the server can be initiator to deliver this
ack message to client because the ack message are all transmitted in http
response. It can only be redelivered when the client sends request again.
> 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)
