000036465 - RSA Identity Governance & Lifecycle Access Fulfillment Express (AFX) server is not running in the UI but afx status says AFX is running

Document created by RSA Customer Support Employee on Jun 23, 2018Last modified by RSA Customer Support Employee on Jul 13, 2018
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000036465
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Product/Service Type: Access Fulfillment Express (AFX), User Interface
RSA Version/Condition: 7.0.2 and higher
IssueA once working AFX server goes into a state of not running and all the connectors are in a stopped state.

Additional Symptoms



  • The afx status command indicates that AFX is running.
  • No changes have been made to the system.
  • There may be connection refused errors in the esb.AFX-INIT.log but the other AFX logs and the aveksaServer.log have no errors.
  • The message below is seen repeatedly in the aveksaServer.log file:


[com.aveksa.afx.server.service.AFXServerAgentServiceProvider] getServerAgentUptimeDate: Removing the uptime date for server
agent 1 - prior uptime date: null, prior last polled date: null, last polled date: 2018-06-12 19:08:56.0, current date: 2018-06-
12 20:25:35.0, polling interval 5000
CauseThere is a locking problem with the T_AV_AFX_SERVER_AGENT table which is an internal database table that logs information about the AFX agent that runs the AFX server.
A product defect has been raised with engineering on this issue.
ResolutionEngineering is working on a permanent fix for this issue.
WorkaroundTo resolve this problem, the database needs to be restarted, as well as RSA Identity Governance & Lifecycle and AFX in the proper order, as shown here:
 

afx stop
acm stop
acm stopdb
acm startdb
acm start
afx star
t


 

Attachments

    Outcomes