Posted: Wed Oct 08, 2014 1:07 am Post subject: Issue when multiple compute nodes access DB
Acolyte
Joined: 23 May 2006 Posts: 56
We are migrating one of the message flows from MB 6.1.x to 8.0.0.4 and getting an issue with flows having multiple compute nodes accessing DB using the same DSN.
We are getting the error message “Transaction will be committed, but a pending automatic transaction exists” whenever the first transaction is send to the flow. I have searched the entire forum on the error message and have found many discussions on similar situation where compute node using propagate with DB access may result in this. We have a similar situation, where the first compute node propagates to the next one and the second node also accesses the DB. But what is confusing to me is why we are getting this error only for the first transaction (every time we restart or redeploy) alone and works fine for the subsequent transactions! Please let me know if any of you have faced similar issues or !
Also, the same flow used to work fine with 6.1.x, not sure this change was introduced in any of the later version! Any idea?
Joined: 04 Oct 2010 Posts: 220 Location: Somewhere in the World....
I had faced this issue long back when I was using 7.0.0.4. I remember that time I was trying to update the DB table and also setting as Commit using Passthru statement. Please check your compute node Transaction mode as well as MQ Input node Transaction mode if the flow started with it.
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