How to create a new ActiveMQ KahaDB for use with AFX in RSA Identity Governance & Lifecycle
Originally Published: 2020-02-26
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Issue
- AFX connectors remain in a Deployed state.
- ActiveMQ will not start.
- Error messages referencing kahadb are in the activemq.log file.
Resolution
- Login as the afx user.
- Stop AFX.
- Navigate to the directory where the ActiveMQ KahaDB database exists.
- Remove the existing KahaDB database.
- Restart AFX. This will create a new KahaDB database.
afx stop cd $AFX_HOME/activemq/data mv kahadb kahadb.old afx start
Related Articles
Running AFX Connectors fail, connectors remain in "Not Deployed" state in RSA Governance & Lifecycle 1.15KNumber of Views How to install Access Fulfillment Express (AFX) for use with RSA Identity Governance & Lifecycle 1.3KNumber of Views RSA Authentication Manager services failed to start after activating a new console certificate 583Number of Views What are the recommended ulimit settings in /etc/security/limits.conf for use with RSA Identity Governance & Lifecycle 231Number of Views Adding a new Fortinet RADIUS dictionary to RSA RADIUS for RSA Authentication Manager 1.3KNumber of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x
Don't see what you're looking for?