How to create a new ActiveMQ KahaDB for use with AFX in RSA Identity Governance & Lifecycle
Originally Published: 2020-02-26
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
What are the recommended ulimit settings in /etc/security/limits.conf for use with RSA Identity Governance & Lifecycle 225Number of Views How to install Access Fulfillment Express (AFX) for use with RSA Identity Governance & Lifecycle 1.27KNumber of Views Running AFX Connectors fail, connectors remain in "Not Deployed" state in RSA Governance & Lifecycle 1.12KNumber of Views RSA Authentication Manager services failed to start after activating a new console certificate 554Number of Views When replacing an RSA SecurID software token with a new software token the token PIN is not carried over to the new token 622Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?