MySQL Forums
Forum List  »  Database Administration & Monitoring

Advanced Search
New Topic

Cannot commit because a nested transaction was rolled back - how to find out which transaction?
Posted by: Rainer Wagner
Date: September 30, 2014 03:35AM

Hi,

unfortunately we get the error "Cannot commit because a nested transaction was rolled back" several times a day in our application. Is there a way to find out which transaction causes the problem?
We are using MySQL 5.5.27 on a Amazon RDS m2.xlarge (2 CPUs and 17 GB Memory).
Additional Info: Symfony 1.4 / Propel / PHP 5.4

thank you!

Navigate: Previous Message• Next Message
Options: Reply• Quote


Subject
Written By
Posted
Cannot commit because a nested transaction was rolled back - how to find out which transaction?
Rainer Wagner
September 30, 2014 03:35AM
Re: Cannot commit because a nested transaction was rolled back - how to find out which transaction?
Peter Brawley
September 30, 2014 10:25AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.