RSA Identity Governance & Lifecycle log message "Could not find new XAResource" in server.log file
Originally Published: 2016-07-01
Article Number
Applies To
RSA Product/Service Type: Hardware/Software appliance
RSA Version/Condition: 6.9.1, 7.0.0, 7.0.1, 7.0.2
Platform: JBoss, WildFly
Issue
RSA Identify Governance and Lifecycle 6.9.1
After a server crash or failure, the following WARN level log message is showing in the /home/oracle/jboss/server/default/log/server.log:07/01/2016 15:23:57.973 WARN (Thread-5) [com.arjuna.ats.jta.logging.loggerI18N]
[com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa]
[com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa]
Could not find new XAResource to use for recovering non-serializable XAResource
< 131075, 32, 30, 1--3f578c42:3cfe:575fa45a:bde262-3f578c42:3cfe:575fa45a:bde263 >
RSA Identity Governance and Lifecycle 7.0.x
After a server crash or failure, the following WARN level log message is showing in the/home/oracle/wildfly/standalone/log/server.log:
2018-08-07 11:28:05,797 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord
< resource:null, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a61ad18:-3a49bebf:5af66b38:1d9c5c, node_name=1, branch_uid=0:ffff0a61ad18:-3a49bebf:5af66b38:1d9c5e,
subordinatenodename=null, eis_name=java:/jdbc/WPDS >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Oracle/Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics
and Real Application Testing options, jndiName: java:/jdbc/WPDS com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@677ba1d6 >
2018-08-07 11:28:05,797 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016038: No XAResource to recover < formatId=131077, gtrid_length=29, bqual_length=36,
tx_uid=0:ffff0a61ad18:-3a49bebf:5af66b38:1d9c5c, node_name=1, branch_uid=0:ffff0a61ad18:-3a49bebf:5af66b38:1d9c5e, subordinatenodename=null, eis_name=java:/jdbc/WPDS >
Cause
Resolution
- Stop the application server services:
acm stop
- As the oracle user, move (rename) the corrupted JMS tx-object-store directory to a backup folder. On startup, the server will create a new empty folder to store the new object store.
-
For version 6.9.1
mv /home/oracle/jboss/server/default/data/tx-object-store /home/oracle/jboss/server/default/data/tx-object-store_backup_ddmmyyy
-
For version 7.0.0
mv /home/oracle/wildfly/standalone/data/tx-object-store /home/oracle/wildfly/standalone/data/tx-object-store_backup_ddmmyyy
- Start the application server services:
acm start
Notes
Related Articles
Error message displayed when deleting a database object via listuclass (Error: 'Can't find object with a DN of...') Number of Views Error when running RSA Via Lifecycle & Governance 7.0 customizeACM.sh: Could not find Aveksa ear Number of Views SailPoint Identity IQ to RSA Authentication Manager API Connection Fails with Error 'Could not Find the Realm: SystemDomain' Number of Views Online, Reinstall Required message on Web Tier after reinstalling with the new RSA Authentication Manager 8.x Web-Tier pac… Number of Views RSA Authentication Agent 7.x for Web for Apache on Red Hat 5 throws error 103: Response to New PIN Request took too long e… Number of Views
Trending Articles
An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
