000038781 - What is 'AFX fulfillment state V' that is sometimes seen in the AFX log in RSA Identity Governance & Lifecycle?

Document created by RSA Customer Support Employee on Apr 24, 2020Last modified by RSA Customer Support Employee on Apr 24, 2020
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000038781
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.0
IssueThe $AFX_HOME/esb/logs/esb.AFX-MAIN.log file has the following error

2020-03-20 17:10:25.019 [INFO] org.mule.module.scripting.component.Scriptable:193 -
AFX fulfillment state V request successful for message 2730163a-87d3-4bfb-97ab-81619d89c2e4
(cr 99999)

Requests in this state can also be seen with the following query executed as avuser:

select * from t_av_afx_request where state ='V'

What is the meaning of AFX fulfillment state V?
ResolutionState V means Valid. It means the AFX request has been sent from RSA Identity Governance & Lifecycle to AFX and is now queued in the AFX connector JMS queue (ActiveMQ). The V state is maintained by AFX until it is able to complete the request. The request will stay in V state (queued in the JMS queue) until the AFX connector has the capacity to pick it up.
NotesIf you experience AFX requests being stuck in the V state, this could indicate a problem with the internal JMS queue (ActiveMQ) used by AFX. Please see related RSA Knowledge Base Article C000038780 -- Change Requests stuck in the AFX Fulfillment Handler Workflow Node and Workflows Stalled in RSA Identity Governance & Lifecycle if you have AFX requests stuck in the V state and you suspect the JMS queue.