RSA Identity Governance & Lifecycle log message "Could not find new XAResource" in server.log file
Originally Published: 2016-07-01
Last Modified: 2023-10-06
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
RSA Authentication Manager services failed to start after activating a new console certificate 595Number of Views "No configured interfaces were detected" error after finishing Quick Setup on a new RSA Authentication Manager 8.4 server 533Number of Views How to create a new ActiveMQ KahaDB for use with AFX in RSA Identity Governance & Lifecycle 374Number of Views Migrating an RSA Authentication Manager 8.x deployment to a new location with different network settings 321Number of Views Adding a new Fortinet RADIUS dictionary to RSA RADIUS for RSA Authentication Manager 1.31KNumber of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide User Application Portal Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device
Don't see what you're looking for?