000027952 - RecoverAtomicAction: transaction not activated unable to replay phase 2 commit after reboot of running system using RSA Via Lifecycle and Governance (L&G)

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000027952
Applies ToRSA Product Set: RSA Via Lifecycle and Governance (Via L&G)
RSA Version/Condition: All
IssueUnable to log-in after reboot of a running system.
The symptom for this problem is the inability to log in. There may be a "migration required" error in the User Interface (UI) and the following error may be seen in the /home/oracle/jboss/server/default/log/server.log:

WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.RecoverAtomicAction_4] - 
RecoverAtomicAction: transaction not activated, unable to replay phase 2 commit




 
CauseThere were numerous files in /home/oracle/jboss/server/default/data/tx-object-store/HashedActionStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction that were 0 bytes in size.
The WARNING message from the log file appears when the writes of transactional object state to the persistent store have failed. This will create the corrupt records in the store, probably zero length files. The recovery process tries to retrieve the transactional object state so that it can recreate the relevant object in memory. This transaction object may be a transaction, a participant record or some other type of object. Since the records are corrupt this is going to keep failing and the recovery manager will keep retrying and failing.
ResolutionThe most common cause for this problem is the disk is full. 
Verify and free up space before proceeding with the following steps.
1. Stop the application server:
$> sudo service aveksa_server stop

2. Execute the following commands in the following /home/oracle/jboss/server/default/data DIRECTORY to list the zero-length files:
$> cd /home/oracle/jboss/server/default/data
$>
find . -size 0 -type f -ls

3. Execute the following to DELETE the zero-length files (Note:  This only deletes files in this directory that have a zero-length (0 bytes) file size):
find . -size 0 -type f -delete

After this command is is run, the errors in the server log will stop once the application server is re-started.
4. Restart the application server
sudo service aveksa_server start
Notes
 

Attachments

    Outcomes