000034590 - AFX connectors cycle between Running, Deployed, Not Deployed and Stopped states in RSA Identity Governance & Lifecycle 6.9.1

Document created by RSA Customer Support Employee on Dec 21, 2016•Last modified by RSA Customer Support on Oct 28, 2019
Version 22Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000034590
Applies ToRSA Product Set: Identity Governance & Lifecycle 
RSA Version/Condition: 6.9.1
 
IssueAfter adding more AFX connectors in RSA Identity Governance & Lifecycle, not all connectors go to the Running state. Some connectors are Running, some are Deployed, some are Not Deployed and some may be Stopped.
 

Example:



User-added image


The AFX log files have multiple errors, such as in the examples below:
  • In the $AFX_HOME/mule/logs/ mule_ee.log:  


java.io.FileNotFoundException: <file location/file name> (Too many open files)


  • In the $AFX_HOME/mule.AFX-INIT.log:


org.apache.commons.httpclient.HttpMethodDirector:197 - 
I/O exception (java.net.SocketException) 
caught when processing request: Too many open files
2016-11-23 00:03:35.669 
[INFO] org.apache.commons.httpclient.HttpMethodDirector:197 - Retrying request


Note: This problem has not been seen in version 7.x. However, if this problem is suspected, note that the AFX log file names and locations have changed slightly in version 7:
 
$AFX_HOME/esb/logs/ mule_ee.log
$AFX_HOME/esb/logs/ esb.AFX-INIT.log
CauseThe key error here is:

Too many open files


The afx user has reached the open file limit.
ResolutionIncrease the number of open files the afx user is allowed to have open at one time by following the steps in 000034242 -- "Too many open files" and other Unix errors seen in RSA Identity Governance & Lifecycle 6.9.1 logs after deploying P15 If the afx user is some other user than the oracle user, substitute the name of the afx user in place of the oracle user in the instructions.

Attachments

    Outcomes