Jboss 7.4: ARJUNA016037 warning and how to clean up, old, crashed two-phase commit (XA) transaction involving ActiveMQ Artemis

That ARJUNA016037 warning means JBoss/WildFly’s transaction manager (Arjuna/Narayana) is trying to clean up an old, crashed two-phase commit (XA) transaction involving ActiveMQ Artemis. Because Artemis isn’t starting, the transaction manager can’t find the message broker (java:/JmsXA) to ask it if the transaction was ever completed. This has created a deadlock or a blocking loop during startup.

From Jboss cli we can ist all transaction UIDs currently held in the store:

/subsystem=transactions/log-store=log-store:read-children-names(child-type=transactions)

Then we can dele only one transaction for example one identified by UUID 0:ffffc0a8067b:b4c47d4:695fa743:e93048

Note that the : has to be escaped under jboss-cli

 /subsystem=transactions/log-store=log-store/transactions=0\:ffffc0a8067b\:b4c47d4\:695fa743\:e93048:delete

If we want to clean the transaction store completely then use the following bash script

#!/bin/bash

# Define your JBoss CLI path (Update this path to your actual JBoss bin directory)
JBOSS_CLI="../jboss/bin/jboss-cli.sh"
CONTROLLER="localhost:9992"

echo "Probing transaction log-store..."
$JBOSS_CLI --connect --controller=$CONTROLLER --command="/subsystem=transactions/log-store=log-store:probe()"

echo "Fetching active transactions..."
TX_LIST=$($JBOSS_CLI --connect --controller=$CONTROLLER --command="/subsystem=transactions/log-store=log-store:read-children-names(child-type=transactions)" | grep '"' | tr -d '", ')

if [ -z "$TX_LIST" ]; then
    echo "No stuck transactions found to delete."
    exit 0
fi

for tx in $TX_LIST; do
    # Escape the colons so the JBoss 7.4 parser reads it as a single node name
    escaped_tx=$(echo $tx | sed 's/:/\\:/g')
    echo "Deleting transaction: $tx"
    $JBOSS_CLI --connect --controller=$CONTROLLER --command="/subsystem=transactions/log-store=log-store/transactions=$escaped_tx:delete"
done

echo "Transaction purge complete."