Bug #73594 ClassCastException in MysqlXADataSource if pinGlobalTxToPhysicalConnection=true

Submitted: 15 Aug 2014 7:26 Modified: 10 Sep 2014 1:07
Reporter: Alexander Soklakov Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / J Severity:S3 (Non-critical)
Version:5.1.32 OS:Any
Assigned to: Alexander Soklakov CPU Architecture:Any

[15 Aug 2014 7:26] Alexander Soklakov
Description:
This is a regression of Bug#62577, fix introduced in c/J 5.1.32 missed on ConnectionImpl occurrence in case pinGlobalTxToPhysicalConnection set to true.

How to repeat:
Try to create XA connection with load-balanced URL and pinGlobalTxToPhysicalConnection=true (see David Martín's comment in Bug#62577).

Suggested fix:
Replace the missed cast to com.mysql.jdbc.ConnectionImpl with cast to com.mysql.jdbc.Connection in MysqlXADataSource as in previous patch.
[10 Sep 2014 1:07] Daniel So
Added the following entry to the Connector/J 5.1.33 changelog:

"XA connections failed with a class cast exception for a load-balanced configuration with pinGlobalTxToPhysicalConnection=true. This was because some XA-related classes used com.mysql.jdbc.ConnectionImpl in method parameters during calls. This fix makes the classes use com.mysql.jdbc.Connection instead in those cases."

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
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.