(7.4.z) JBJCA-1467 - Possible data inconsistency when CMR fails at Commit phase

Steps to reproduce on postgreSQL: Prerequisites: byteman installed byteman script "InjectFailureToCommit.btm" downloaded (Can be found in attachements) (This script injects the failure to java.sql.Connection.commit(), the rule is applied only the first time the method is called) Adjust standalone.conf for JAVA_OPTS to include byteman JVM args (Replace paths with your path to byteman and provided script) -javaagent:/PATH/TO/BYTEMAN/lib/byteman.jar=script:/PATH/TO/SCRIPT/InjectFailureToCommit.btm,sys:/PATH/TO/BYTEMAN/lib/byteman.jar -Dorg.jboss.byteman.transform.all=true" Start server: ./standalone.sh -c=standalone-full.xml Configure server to use postgres CMR datasource using jboss-cli (use your paths and database connection info) module add --name=postgresql --resources=PATH/TO/DRIVER/postgresql-42.5.0.jar --dependencies=javax.api,javax.transaction.api /subsystem=datasources/jdbc-driver=postgresql:add(driver-name=postgresql, driver-module-name=postgresql, driver-class-name=org.postgresql.Driver) /subsystem=datasources/data-source=postgresDS:add(driver-name="postgresql",jndi-name="java:/postgresDS", connectable="true", connection-url="jdbc:postgresql://DB_URL:PORT/DATABASE_NAME",user-name="USER",password="PASSWORD") /subsystem=transactions/commit-markable-resource="java:/postgresDS":add(name=xids) Add table to DB for the CMR CREATE TABLE xids (xid bytea, transactionManagerID varchar(64), actionuid bytea) Deploy adjusted CMT QS git clone -b CMRCommitFailureReproducer74 git@github.com:OndrejGerzicak/quickstart.git cd quickstart/cmt mvn wildfly:deploy Test the wrong behaviour Check list of customers (There is only Tom) Create customer (eg. John) Error appears (ignore the message of already existing user, that is just implementation of this QS that something went wrong. You can see in the log of server, that SQLException and also RollbackException was raised Check list of customer again. You can see that even though exception was raised and error appeared the customer is persisted in the DB.