Error DatabaseTransactionOutOfOrderException: in DatabaseConnection->rollback()

Are you on Drupal 7.8?

I don't suppose you're still getting this error or have found a fix? I've still never seen the error.

You might also provide other helpful information about your installation - i.e. MySQL version, contributed modules, etc.

Weird, but glad to hear it. : )

for reference: the coupon fix in #1315022: Emptying cart with coupon applied throws error made me happy with this

Sometimes I got the same error when users do the order (about 1 time for 50 orders). If I try to reproduce this error with same order, it isn't reproduced. So seems this issue is related to browser or cookie (maybe specific commerce cart actions) on client side.
I don't use Commerce Coupon module, Commerce is 1.3 version.

I am getting this error in combination with the commerce_discount module.
The following error from the commerce_discount module:
Notice: Undefined index: discount_name in commerce_discount_remove_discount_components()
See the issue
(unfortunately the patch is not working, but i am looking in to this).

This generates the error mentioned above:
DatabaseTransactionOutOfOrderException: in DatabaseConnection->rollback() (line 1042

The error is generated when adding a product to the cart. A pricing rule is used with a product variation field as discount parameter. When selecting "base price" everything works perfect, but the discount does not show in the cart overview.

The error seems to be related to that module, so no need to reopen a duplicate issue here.

I am getting this error quite often now. I am not using commerce_discount.

This issue is so old I doubt it can be the same one as initially reported. I do believe there is still an open issue pertaining to database transactions, so I'm going to close this one out. You might also look in the core Drupal queue.

I ran into this issue again and tried updating Commerce Discounts again and this time the issue was resolved.

I've created a new discount where you get one product for free when you purchase a certain amount of a certain product. First I add one of the required product to the cart and when I update the quantity of that product in the cart I get the following error:

DatabaseTransactionOutOfOrderException: in DatabaseConnection->rollback() (line 1061 of includes/database/database.inc)

I've backtracked this to when the save method is being performed in commerce_order.controller.inc.
This does not occur when the discount condition is not fulfilled.

Did you install and enable the commerce_addressbook module?

/**
 * Implements hook_commerce_order_insert().
 */
function commerce_addressbook_commerce_order_insert($order) {
 ....
}

This hook impelements maybe is the cause.

No. We don't use the commerce_addressbook module.

I still have this error, though i disabled commerce_adressbook module.

DatabaseConnection->rollback() (line 1058 in /srv/apps/events/event/includes/database/database.inc).

I have the same problem...
DatabaseConnection->rollback() (line 1061 in...

It seems this problem appears after setting a pricing rule. The price is multiplied by 0.7 if user role is Revendeur.
The price are correctly calculated but impossible to add a product in the cart.
Delete the rule don't change anything !
The problem is solved after disabling commerce_discount...

My drupal core is 7.33 and commerce kickstart version is 7.x-2.19..

Same result with dev version of commerce_discount...

This said, the "revendeur" price is calculated correctly without commerce_discount... so...

This may have nothing to do with discounts. I found this thread while searching for inexplicable DatabaseTransactionOutOfOrderException errors on saving an order.

It seems that the save() method in commerce_order.controller.inc calls an unncecessary $transaction->rollback() if the parent::save fails. It's redundant because parent::save itself does a rollback. Thus calling another one trips the if ($rolled_back_other_active_savepoints) condition in database.inc.

What this means is that the DatabaseTransactionOutOfOrderException error is masking another error that is therefore not being logged.

I had this and it was because I was modifying the order_number through a rule but didn't check for duplicates and it was doing an integrity violation then rolling back.

Just faced the same issue. In our case the problem was with saving decimals to postgres integer fields. tailing postgres log has shown nice error message ERROR: invalid input syntax for integer: "333.33333333333" at character 246. Fixing it made the error go away. Just my $.02...

Patch seems to be against commerce_addressbook so moving back.

So, I'm just closing this. There's so many comments of users who probably landed here via Google trying to find an answer to this crazy error (which I don't blame any of them.) It's old and who knows its root cause.

Please, if you come here have specific error logs or MySQL logs that point to a query related to this module.

Hi,

I have added product into the cart and clicked on Proceed to checkout button. I am getting same error on /chechkout page.

DatabaseTransactionOutOfOrderException: in DatabaseConnection->rollback() (line 1061 of /path/to/project/includes/database/database.inc).

I am using Drupal 7.39 with commerce version 7.x-1.8.

Anybody has solved this issue?

Thank you @joelpittet for #20!!! I forget that this always happens to me when I copy down my production database to my development environment, where I'm saving over order numbers with different order numbers generated by a 3rd party fulfillment API. The 3rd party's dev API always sends back order numbers that already exist in the production data, so when it tries to save an order number that already exists, it blows up. This DatabaseTransactionOutOfOrderException isn't exactly super helpful at telling me that, though.

Anyone else Google-ing this issue, mine ended up being an issue with Commerce Message where I had a custom rule sending emails out when an admin message was left on the order. I had to set the ""Send Message with Message notify"" to FALSE on "Save on Success/Fail" in the custom rule and the error went away.