Mule request-reply - why can't we use transactional VM or JMS inside the scope -


mule doc says that, vm or jms connectors set transactional can’t used inside request-reply scope. not understand well.

can 1 please explain example?

what trying achieve? url point explains why isn't possible.

vm or jms connectors set transactional can’t used inside request-reply scope. both vm , jms connectors allow perform transactions of several different types, none of these compatible how request-reply scope works. this because request sent out request-response isn’t sent until transaction committed – transaction in turn not committed until entire flow has been executed (including execution of request-response scope). leads situation both processes blocking each other: flow isn’t executed because it’s still waiting response on request-reply scope, response never arrive since request hasn’t been sent yet (as mentioned before, message sent once transaction committed).


Comments

Popular posts from this blog

java - Static nested class instance -

c# - Bluetooth LE CanUpdate Characteristic property -

JavaScript - Replace variable from string in all occurrences -