There are two workarounds needed:
- Restart the stuck AFX requests, and
- Manually modify the ActiveMQ memory configuration to prevent future occurrences of this issue.
Restart stuck AFX requests:
Open a support ticket with
RSA Identity Governance & Lifecycle Support for a workaround and provide the following information in the case:
- Login to a SQL tool such as SQL*Plus or SQL Developer as avuser, and
- Execute the following queries:
These queries will determine the AFX request state of the specific stuck change request:
select * from T_AV_CHANGE_REQUESTS CR where NAME like '%stuck-change-request-name%';
Note the values of CR.ID and CR.CURRENT_STATE returned in the query results and substitute them into the next two queries:
select * from T_AV_CHANGE_REQUEST_DETAILS CRD where CHANGE_REQUESTS_ID=<CR.ID>
select * from T_AV_AFX_REQUEST where change_item_id=<CRD.ID>
This query will identify any AFX requests in the V state:
select * from t_av_afx_request where state ='V'
Manually modify the ActiveMQ memory configuration:
- Follow the instructions in the attached ActiveMQ_Memory_Changes.docx document.
- Restart AFX as the afx user:
afx restart
