cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Riedlinger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-6323) WS-RM redelivery not implemented
Date Mon, 30 Mar 2015 13:14:53 GMT

     [ https://issues.apache.org/jira/browse/CXF-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Riedlinger updated CXF-6323:
-----------------------------------
    Description: 
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. Unfotunately
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.;-)


  was:
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. Unfotunately
that never happens.

Debugging the problem and taking a look into the source code I found that code:


private void reconverDestinationSequence(Endpoint endpoint, Conduit conduit, Destination d,

                                             DestinationSequence ds) {
        d.addSequence(ds, false);
        //TODO add the redelivery code
    }


It would be nice if someone could correct/implement this;-)

Befor that you the WS-RM implementation is not reliable.;-)



> 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.
Unfotunately 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)

Mime
View raw message