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 the line 101 if we don't know the cxf version. In any case, if you don't (or can't configure a decoupled ep because of your firewall rules), you should stick to oneway calls and setting AcknowledgementInterval to 0 so that you get your request ack'ed in its response. If you have further questions, please describe your scenario in more details (version, req/resp or oneway, etc). And i don't know what your conduit is doing. So it's really hard what to say based on the info you provided so far. 2013/5/29 Juan Alberto Lopez Cavallotti <[email protected]> > 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 printing the > following log statement: > > WARN 2013-05-27 16:57:33,917 [RMManager-Timer-2051976295] > org.apache.cxf.endpoint.DeferredConduitSelector: > MessageObserver not found This is actually happening on line: 101 of the > class org.apache.cxf.endpoint.AbstractConduitSelector > > I would like to diagnose the cause of this situation. > > Please find attached my configuration file. > > Thanks for your help in advance. > > Regards, > Juan Alberto López Cavallotti >
