As per Redhat's official documentation, in EAP 6 there is a proper documented way of removing stale transaction records from the store. This works with all transaction store formats i.e. os file, hornetq aio and jdbc.
1. Log into jboss-cli
jboss-cli.sh -c --user=<USERNAME> --password=<PASS>
2. Refresh the transaction store
[[email protected]:9999 transactions] /subsystem=transactions/log-store=log-store/:probe()
3. List all transactions
[[email protected]:9999 transactions] ls /subsystem=transactions/log-store=log-store/transactions
4. Then delete the one that is causing the warning
[[email protected]:9999 transactions] /subsystem=transactions/log-store=log-store/transactions=0:ffffa409cc8a:1c01b1ff:5c7e95ac:eb:delete()
{"outcome" => "success"}
For Identity Suite / vApp implementation, we must ensure the application server user is created first
1. Create JBoss CLI user:
For Identity Manager:
cd /opt/CA/wildfly-idm/bin
For Identity Governance:
cd /opt/CA/wildfly-ig/bin
sudo ./add-user.sh -s -u jbossadmin -p <PASS>
2. Connect to JBoss CLI (interactive)
For Identity Manager:
/opt/CA/wildfly-idm/bin/jboss-cli.sh -c --user=jbossadmin --password=<PASS>
For Identity Governance:
/opt/CA/wildfly-ig/bin/jboss-cli.sh -c --user=jbossadmin --password=<PASS>
And continue with the steps above to delete the relevant stale transaction
Note:
If you receive an error message while running the delete "delete is not a valid operation name" try the command as following:
/subsystem=transactions/log-store=log-store/transactions=0\:ffffa409cc8a\:1c01b1ff\:5c7e95ac\:eb:delete()