• Change requests that provision using AFX are stuck in the fulfillment phase.
• The change request workflows are stuck in the AFX fulfillment handler node.
• Workflows are flagged as stalled.
• AFX requests are stuck in the V state.

• RSA Identity Governance & Lifecycle 7.1.1 P07
• RSA Identity Governance & Lifecycle 7.2.0 P02
• RSA Identity Governance & Lifecycle 7.2.1
• RSA Identity Governance & Lifecycle 7.5.0

1. Restart the stuck AFX requests, and
2. Manually modify the ActiveMQ memory configuration to prevent future occurrences of this issue.

Restart stuck AFX requests:

1. Login to a SQL tool such as SQL*Plus or SQL Developer as avuser, and
2. Execute the following queries:

select * from T_AV_CHANGE_REQUESTS CR where NAME like '%stuck-change-request-name%';

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:

1. Follow the instructions in the attached ActiveMQ_Memory_Changes.docx document.
2. Restart AFX as the afx user:

afx restart