Posted: Mon Jan 11, 2021 8:14 am Post subject: Rollbacking DB transactions when the input node is HTTP i/p
Novice
Joined: 26 Mar 2019 Posts: 10 Location: Hyderabad,India
Hi All,
Hope you are doing well!
We have a requirement that we have to insert data in the three tables at a time (All or none) and commit should happen if three inserts are successful.
Message Flow
Http Input--(out)-->Compute1-->Route to label label--->Subflow--> Http Reply
Http Input--(Failure and Catch)-->Exception handler
subflow
input-->Comput2-->output
Compute 2 transaction mode property set to "Automatic" (default)
DB insert query logics are written at Compute 2
As far as I know commit and rollback should be handled by the integration node as these are broker coordinated transactions . Commit should happen if the transaction is completed successfully. (Please correct me if am incorrect)
But I have observed that DB transactions are committed even though exception raised in the IIB application (Transaction is not completed)
The DB transactions are roll-backing in case of exception if the failure and catch terminals of HTTP input are not connected.
Here my requirement is DB tran Rollback should happen incase of exception even if Failure and catch Terminals of HTTP input are connected.
Also (before anybody else mentions it) HTTP is not a transactional protocol, so you should consider writing the HTTP request onto a queue as early as possible.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum