Defect HC-15791
DeployContractCmdImpl commits but does not begin a new transaction.
Software
| Customer case | Applies to | Corrected in |
|---|---|---|
| CS0296648 | V8.0.4.25 | 8.0.4.29 |
Observed behavior
In some situations, if a transaction exists at the start of DeployContractCmdImpl, the transaction will be committed without a new one being started for the remaining work.
Expected behavior
There should always be a match between transaction begin and commit. Situations can occur where there are either zero or multiple transactions started and committed. If there is an existing transaction on entry to the code, it might be committed before it should be, and no additional transaction is started.
Resolution
The code was updated to properly balance the transaction begin/commit logic.