Question
Synechron
US
Last activity: 14 Nov 2016 5:15 EST
Could not commit when auto commit set on
Hi.
I'm doin a obj-save without write now/immidiate. Then I have a called "CommitWithErrorHandling" OOTB acitivity.
However I get a error in the commit step stating that
" There was a problem committing a transaction on database PegaRULES: code: 17273 SQLState: 99999 Message: You cannot commit with auto-commit set.
I have changed my DSS value to false as well. But still i am getting the same error.
DATA-ADMIN-SYSTEM-SETTINGS PEGA-RULES!DATABASE/AUTODBSCHEMACHANGES
Can anyone plese help me, whats the exact issue, and how to resolve this.
***Updated by Moderator: Lochan. Removed user added Ask the Expert and helpme tags. Apologies for confusion, shouldn't have been an end-user option***
Accepted Solution
Synechron
US
Hi,
Apologize for the delay. I figured out the issue, Its causing because of the lock issue, Couldnt acquire the locks properly and causes this commit fail error.
Pegasystems Inc.
GB
Hi Sateesh,
Are you getting the error when running your Activity from the Designer Studio or a User Portal ?
The reason to ask: you generally do NOT want to enter in explicit 'COMMITs' within PRPC Activities - you should allow PRPC to handle the Transaction Bounderies for you (essentially as you navigate through Flows in a User Portal, the system will issue the relevant commits for you).
In contrast, when you build and test an Activity in the Designer Studio; there is no automatic explicit commit.
This means you will need to either build two versions of your Activity (perhaps just a 'wrapper' Activity that calls the main Activity and then issues a commit), or perhaps pre-condition on your 'commit' step or something like that - to take into account the two different scenarios.
Accepted Solution
Synechron
US
Hi,
Apologize for the delay. I figured out the issue, Its causing because of the lock issue, Couldnt acquire the locks properly and causes this commit fail error.
TATA Consultancy Services Ltd
GB