what is meaning for state V in AFX log, why fulfillment request gets stuck in state V? anybody encountered same issue?
FYI - After updating status to N, it works sometime, but its not ideal case to keep updating it everytime.
what is meaning for state V in AFX log, why fulfillment request gets stuck in state V? anybody encountered same issue?
FYI - After updating status to N, it works sometime, but its not ideal case to keep updating it everytime.
Thanks Mostafa. Let me check.
Mostafa Helmy it appears the "V" state is maintained by AFX until it is able to complete the request. It was reported that after an AFX restart AFX will attempt to retry any requests in this state, and so restarting AFX should move these requests to completion.
The fix for this issue is targeted for a future release. I will get a KB article created.
Mostafa Helmy do you know if there are any errors in any log files associated with this failure? As far as I can see it is manifest as a performance issue and there are not actual failures (except for the requests staying in "Pending Action").
Yes that is my understanding as well. The request will stay in V state (queued in the JMS queue), till the AFX connector has the capacity to pick it up. So it could be either due to high load on that specific connector or a problem in the internal AFX JMS queue (as in ACM-101553).
I am unaware of any specific errors in this case. As far as I understand, this is just another type of performance problem.
Hello Mostafe, Just to let you know, there is no high load on env, its non-prod env. We see request are getting stuck in valid state, and moving to stalled.
In that case it could be a resource (memory) issue. Usually test environments have very limited, below recommended, resources. The defect I referred to earlier ACM-101553 is actually caused by memory issues in the AFX internal JMS queue. For example if you have an 8GB RAM test server running all 3 of the database, app-server and AFX, you will most certainly hit similar resource problems.
That is just my guess for now, which is why I believe this is best investigated by RSA Support.
Hi Ian,
Can you share a Jira ticket number around this one until the KB is created?
State V means "Valid”. It means that the AFX request has been sent from IGL to AFX and is now queued in the connector's JMS queue.
If you experience AFX requests being stuck in the V state, this might indicate a problem with the internal JMS queue (activemq) used by AFX. Please log a case with RSA support and reference this post and ACM-101553 as a potential cause.