Bug #44687 | XA Transactions dissapear - almost | ||
---|---|---|---|
Submitted: | 6 May 2009 10:23 | Modified: | 6 May 2009 10:54 |
Reporter: | Karl Jorgensen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
Version: | 5.1.32 | OS: | Linux (5.1.32-community-log, RHEL 5.2) |
Assigned to: | CPU Architecture: | Any | |
Tags: | xa |
[6 May 2009 10:23]
Karl Jorgensen
[6 May 2009 10:24]
Karl Jorgensen
Output from "show engine innodb status"
Attachment: show-engine-innodb-status.txt (text/plain), 16.94 KiB.
[6 May 2009 10:52]
Karl Jorgensen
Strange: Re-starting the database cleared out the XA transactions !? Not sure why, but I'm happy.
[6 May 2009 10:54]
Karl Jorgensen
Closing this. Rationale: * There is very little debug information available to developers * Restarting the database "solved" the problem. * Restarting the database probably made it impossible to obtain more diagnostic information
[6 May 2009 11:57]
Sergei Golubchik
If you'll be able to repeat it by doing something in your JBoss application, you can try to enable MySQL general query log (mysqld --log) which will log all incoming statements into a file, it could help to create a "pure" test case in MySQL.
[29 Sep 2010 16:05]
Brett Cave
Hi, I have the same problem, in 5.1.42 rhel5 The first line echo's the statement that is executed by mysql -e in the 2nd command: [root@qa-db-01 ~]# echo "xa rollback '`mysql --skip-column-names -e 'xa recover' | head -1 | awk '{ print $4 }'`'" xa rollback '1--3f57b3af:8546:4c6d3534:4146d-3f57b3af:8546:4c6d3534:41472' [root@qa-db-01 ~]# mysql -e "xa rollback '`mysql --skip-column-names -e 'xa recover' | head -1 | awk '{ print $4 }'`'" ERROR 1397 (XAE04) at line 1: XAER_NOTA: Unknown XID The state occurred when either the disk that the mysql data dir was mounted on filled up or by killing the mysqld process without a clean shutdown. Going to keep the db server up for diagnosis.