Salesforce

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

Header
What is 'AFX fulfillment state V' that is sometimes seen in the AFX log in RSA Identity Governance & Lifecycle?
What-is-AFX-fulfillment-state-V-that-is-sometimes-seen-in-the-AFX-log-in-RSA-Identity-Governance-Lifecycle
What is 'AFX fulfillment state V' that is sometimes seen in the AFX log in RSA Identity Governance & Lifecycle?
Work in Progress
1,467.89
Article Content
 
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.0
 
The $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?
 
State 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.
 
If 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.


 
000038781
Article Settings
External
Manual
Diane McCoy
4/23/2020 9:17 PM
Article Assignment
 
 
 
Article Properties
Published
Knowledge
000058171
Diane McCoy
Katrina Nash
English

Powered by