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
RSA Authentication Manager services failed to start after activating a new console certificate 517Number of Views How to install Access Fulfillment Express (AFX) for use with RSA Identity Governance & Lifecycle 1.22KNumber of Views What are the recommended ulimit settings in /etc/security/limits.conf for use with RSA Identity Governance & Lifecycle 208Number of Views Radius Client Authentication failed For PIN+Token profile (New PIN Mode) with Cisco Anyconnect VPN 580Number 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 609Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?