Bug #13143 XA XID uniqueness not assessed correctly
Submitted: 13 Sep 2005 15:45 Modified: 5 Oct 2005 23:45
Reporter: Paul DuBois Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.x OS:
Assigned to: Sergei Golubchik CPU Architecture:Any

[13 Sep 2005 15:45] Paul DuBois
The XA spec says this about XID uniqueness:

  The only requirement is that both gtrid and bqual, taken together,
  must be globally unique.

However, MySQL also considers the formatID part of the XID
value when assessing uniqueness.

How to repeat:
In one client, issue this statement: XA START 'a','b',1;

In a second client, issue the same statement. This
error will occur:

ERROR 1440 (XAE08): XAER_DUPID: The XID already exists

That's okay (the gtrid and bqual are the same as in client
one, so the XID value is a dup).

However, if you use a different formatID value in the second
client, the statement succeeds.  It should fail, even if the
formatID value is different.
[5 Oct 2005 14:40] Sergei Golubchik
Fixed in 5.0.15
[5 Oct 2005 14:42] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[5 Oct 2005 23:45] Paul DuBois
Noted in 5.0.15 changelog.