MysqlXaConnection.recover(int flags) now
permits combinations of
TMENDRSCAN. To simulate the
“scanning” nature of the interface, we return all
prepared XIDs for
TMSTARTRSCAN, and no new
XIDs for calls with
TMENDRSCAN when not in combination with
TMSTARTRSCAN. This change was made for API
compliance, as well as integration with IBM WebSphere's
MysqlValidConnectionChecker for JBoss
doesn't work with
Added connection/datasource property
pinGlobalTxToPhysicalConnection (defaults to
false). When set to
XAConnections, the driver ensures
that operations on a given XID are always routed to the same
physical connection. This enables the
XAConnection to support
XA START ...
has been called, and is also a workaround for transaction
managers that don't maintain thread affinity for a global
transaction (most either always maintain thread affinity, or
have it as a configuration option).
Fixed driver fails on non-ASCII platforms. The driver was
assuming that the platform character set would be a superset of
latin1 when doing the handshake for
authentication, and when reading error messages. We now use
Cp1252 for all strings sent to the server during the handshake
phase, and a hard-coded mapping of the
language system variable to the character set
that is used for error messages.
Fixed can't use
XAConnection for local
transactions when no global transaction is in progress.
Better caching of character set converters (per-connection) to remove a bottleneck for multi-byte character sets. (Bug #20242)
ConnectionProperties (and thus some
subclasses) are not serializable, even though some J2EE
containers expect them to be.