Showing all 12 (Edit, Save, CSV, Feed)
ID# Date Updated Type Status Sev Version OS CPU Summary
720362014-03-14
2:41
2014-03-14
13:06
Connector / JVerifiedS3AnyAnyXA isSameRM() shouldn't take database into account
752052014-12-13
17:26
2015-01-27
20:00
MySQL Server: XA transactionsVerified
(2095 days)
S25.7.5-m15AnyAnyMaster should write a LOST_EVENTS entry on xa commit after recovery.
780502015-08-13
7:29
2016-12-14
4:54
MySQL Server: Storage Engine APIVerified
(1897 days)
S35.6.26LinuxAnyCrash on when XA functions activated by a storage engine
873852017-08-11
6:32
2017-11-17
1:55
MySQL Server: ReplicationVerified
(1168 days)
S2mysql-5.7.17AnyAnyPartial external XA transactions are not rolled back correctly
873892017-08-11
7:30
2017-11-17
1:56
MySQL Server: ReplicationVerified
(1158 days)
S3mysql-5.7.17AnyAnyReplication position not persisted correctly for XA transactions
875602017-08-28
9:14
2020-01-19
4:13
MySQL Server: XA transactionsVerified
(1044 days)
S2mysql-5.7.17AnyAnyXA PREPARE log order error in replication and binlog recovery
916462018-07-16
4:40
2019-03-19
7:48
MySQL Server: XA transactionsVerified
(829 days)
S25.7.22, 8.0.11AnyAnyxa command still operation when super_read_only is true
916332018-07-13
21:14
2018-10-05
23:14
MySQL Server: ReplicationVerified
(829 days)
S25.7.22Linuxx86Replication failure (errno 1399) on update in XA tx after deadlock
839832016-11-28
8:50
2019-02-18
16:38
MySQL Server: ReplicationVerified
(612 days)
S35.7.13CentOS (6.5)Anyinnodb fail to recover the prepared xa transaction
992052020-04-08
1:36
2020-04-08
11:19
MySQL Server: XA transactionsVerified
(197 days)
S28.0.18, 8.0.19AnyAnyxa prepare write binlog while execute failed
996252020-05-19
7:33
2020-05-20
12:22
MySQL Server: XA transactionsVerified
(156 days)
S35.7Linuxx86Replaying Binary log returns ER_CANT_SET_GTID_NEXT_WHEN_OWNING_GTID
996382020-05-20
0:53
2020-06-09
14:47
MySQL Server: InnoDB storage engineVerified
(135 days)
S58.0.18AnyAnyxa transaction with low performance
Showing all 12 (Edit, Save, CSV, Feed)