Topic 5 :Transaction Management in Mule 4

[@MuleSoftTechZone]

There’s a slight mistake in the slide . Please see the description for ALWAYS_JOIN below The connector will always join the existing transaction. If there is no transaction, or if the current transaction is not compatible with the current operation, the operation will fail to execute.

[@simrangupta1305]

no one can explain like you do every logic much respect sir thankyou.

[@MuleSoftTechZone]

Tqsm 😀

[@bhuvanhanumanthu6232]

Simple and easy to understand, Thanks for the video.

[@saagnikadhikary6582]

I think the "ALWAYS_JOIN" will throw an error if there is no transaction already in progress and not start a new one, as you've mentioned. Could you please check and update on this?

[@MuleSoftTechZone]

Thanks for highlighting It was a slide error . Will be pinning the comment with the correct description

[@LikhithaGopu]

can you please try XA also

[@PolandDiary]

thanks for the information. I have one doubt,why you used try block also with Transaction management, what happen we use with out transaction management with try block and with transaction management with database. please answer to my question... waiting for your reply

[@varshaludhrani6754]

What's the difference between indifferent and none ?

[@Enigmatechphaneendra]

in type XA, there will be multiple transactions right?

[@MuleSoftTechZone]

Multiple resources running on multiple transactions yes

[@chaithanyareddy8381]

where can we identify transaction type in HTTP ? you skipped that one

[@SumitKumar-sg9pt]

HTTP listener does not support transactions hence there is no configuration related to that in the connector.