yeah, I didn't noticed that it's transacted, which is a good option for persistence, I'm not sure but probably you also need to add synchronous="true" on the consumer (because when it's asynchronous transaction ends after sending message not after received status DONE from CXF provider),
but to better answer you question, can you say what do you want to achieve here? is that in-only invocation? if yes but you care if the invocation successful, maybe it's better to design target service to send confirmation, that is make it in-out? if you don't care if target service invocation was successful, then you probably don't need persistence on the bus (just CXF consumer - provider pair), probability that SM crashes during such invocation would be very low, jav1erp wrote: > > thank for your reply > > I've just tried to see how I can keep messages in case of smx crash. Any > idea? > > > -- View this message in context: http://www.nabble.com/operation-name-is-null-after-jms-endpoints-tp21713138p21743258.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
