Re: Question about WS-RM

Hi Dennis, Initially I also thought the storage was simply missing and that was causing the error when the sequence was looked up after restart. But that was not the case. The problem occurred at ws-addressing's request-response correlation using a decoupled endpoint. Juan uses a request-response

Re: Question about WS-RM

2013/6/12 Juan Alberto Lopez Cavallotti juan.cavallo...@mulesoft.com Hi Guys, What is actually my concern is that the message does not get out of the retransmission queue, I've also tried the same case on CXF 2.7.5, and configured the retry policy wsrm-mgr:retryPolicy maxRetries=2 / getting

Re: Question about WS-RM

Hi Guys, What is actually my concern is that the message does not get out of the retransmission queue, I've also tried the same case on CXF 2.7.5, and configured the retry policy wsrm-mgr:retryPolicy maxRetries=2 / getting the exact same behavior. My concern of this is that a server exposing this

Re: Question about WS-RM

Hi Juan, 2013/6/4 Juan Alberto Lopez Cavallotti juan.cavallo...@mulesoft.com Hello Aki, Thanks for your response and for taking the time to review the information I provided. While I'm still processing the answer I can think of two possible solutions: - Changing the model so we use

Re: Question about WS-RM

Hi Aki, That answers my questions, thanks a lot for your help. Regards, Juan MuleSoft On Wed, Jun 5, 2013 at 9:48 AM, Aki Yoshida elak...@gmail.com wrote: Hi Juan, 2013/6/4 Juan Alberto Lopez Cavallotti juan.cavallo...@mulesoft.com Hello Aki, Thanks for your response and for taking

Re: Question about WS-RM

Hi Juan, Thanks for uploading the logs. I am not yet 100% sure but it looks like there is an issue in the response delivery for request-response ws-rm case after an error. As we have several persistent recovery tests for ws-rm, I thought initially the problem after a successful response

Re: Question about WS-RM

Hi Juan, It looks like the problem occurs after the response retransmission from the server at the client side at its decoupled receiving port. Because you have a request-response call, there is a step to correlate this response message to the original exchange. But the old exchange was gone when

Re: Question about WS-RM

Hello Aki, Thanks for your response and for taking the time to review the information I provided. While I'm still processing the answer I can think of two possible solutions: - Changing the model so we use one-way endpoints if WS-RM with decoupled endpoint is present. - Purge the messages from

Re: Question about WS-RM

Hi Juan, your attachment didn't get to the list. Maybe you should put it at some remote storage that hat the http access. and how is your client configured? can you make sure that you configured the decoupled endpoint and persistence at the client? regards, aki 2013/5/31 Juan Alberto Lopez

Re: Question about WS-RM

Hi Aki, Please find the log here: http://pastebin.com/B0TtSduG About the client, it works correctly all the time when I use the CXF facilities outside Mule, this is, connecting to a spring webapp with the same service configured, my goal is to solve this for any type of client, correct or

Re: Question about WS-RM

Hi Juan, I have a couple of questions. You mention of the backchannel, that means you have configured a decoupled endpoint where the server can asynchronously deliver ack messages to? I didn't see it at least in your beans.xml file. And you have a request-response service right? That means there

Re: Question about WS-RM

Hi Aki, Thank you for your reponse. Yes, I have a decoupled endpoint, I have a standalone client based on cxf's sample projects (nothing fancy added) which is currently working fine, I'm killing it randomly so I can handle that kind of outages I'm aware that you also have a custom interceptor

Question about WS-RM

Hello, I have a custom conduit implementation which takes care of the integration of CXF and MuleESB. I am able to use the WS-RM functionality on the happy path over this conduit but when something goes wrong on the backchannel I get the message stuck on the redelivery queue and constantly

Re: Question about WS-RM

I suppose you are seeing this warning because you have configured no separate channel (i.e.d, decoupled endpoint) for acks or response delivery. So when the http response connection is gone, you will get some kind of stuck message until at least the next message comes in. Can't say anything about

Re: Question about WS-RM

Hi Aki, Thanks for getting back to me, if you wish to see the implementation of the conduit, here is a github link for it: https://github.com/mulesoft/mule/blob/mule-3.3.2/modules/cxf/src/main/java/org/mule/module/cxf/transport/MuleUniversalConduit.java What I'm trying to do is to make this