MySQL Bugs: #72036: XA isSameRM() shouldn't take database into account

Bug #72036	XA isSameRM() shouldn't take database into account
Submitted:	14 Mar 2014 2:41	Modified:	19 Oct 15:32
Reporter:	Jess Balint	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / J	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	xa

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
XA isSameRM() defers to ConnectionImpl.isSameResource() this method returns false if only the database differs between connections. There is no known or documented reason for this.

How to repeat:
call isSameRM() on two different connections to the same database server but with different databases

Suggested fix:
remove this comparison

Posted by developer:
 
Added the following note to the Connector/J 9.5.0 release notes:

The isSameRM() method incorrectly considered the database name in 
addition to host and port for resource manager comparison, leading 
to improper identification of the resource manager. 
The database name is no longer included in the comparison logic.