000037483 - Error handling Access Fulfillment Express (AFX) primary request in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 5, 2019Last modified by RSA Customer Support Employee on Feb 13, 2020
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000037483
Applies ToRSA Product Set: RSA Ientity Governance & Lifecycle
RSA Version/Condition: 7.0.2, 7.1.0, 7.1.1
IssueIn RSA Identity Governance & Lifecycle the following WARN level log message is seen in the /home/oracle/wildfly-10.1.0.Final/standalone/log/aveksaServer.log file:

09/11/2018 14:20:25.275 WARN  (default task-94) [com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler] Error handling AFX primary request

at com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler.processFulfillmentRequests(AFXPrimaryRequestHandler.java:330)
CauseThis issue may occur when migrating from RSA Identity Governance & Lifecycle 7.0.1 and earlier to a later version.

The issue occurs if there were any failed Access Fulfillment Express (AFX) requests in the system prior to migration. RSA Identity Governance & Lifecycle 7.0.2 and later will attempt to retry AFX requests that have failed. The AFX requests are stored internally as XML objects and due to a change in format of the XML headers between versions, AFX requests that were generated on a previous version cannot be read. This causes a failure when AFX attempts to resend those requests.

Normally this WARN level log message may be ignored.  
ResolutionThis issue is resolved in the following RSA Identity Governance & Lifecycle versions and/or patch levels. The system will update the XML headers of old requests during migration to prevent this error.
  • RSA Identity Governance & Lifecycle 7.0.2 P14
  • RSA Identity Governance & Lifecycle 7.1.0 P08
  • RSA Identity Governance & Lifecycle 7.1.1 P02
  • RSA Identity Governance & Lifecycle 7.2
NotesNormally this WARN level log message may be ignored.  In some instances if the customer has a very large number of failed AFX requests from before the migration customers may experience performance issues in AFX due to the handling of the failed requests.