This is a known issue in the following version:

• RSA Governance & Lifecycle 8.0.0 
• RSA Governance & Lifecycle 8.0.0 P02

After starting AFX, some AFX Connectors fail to be deployed successfully due to Out of Memory errors.

This is most often seen after an RSA Identity Governance & Lifecycle upgrade or after adding many new connectors to the existing configuration.

esb.AFX-MAIN.log contains the below error:

ERROR 2024-05-27 13:00:05,564 [connection-pool-delays-thread-pool(1)] [processor: PRIMARY_REQUEST/processors/5/route/2/processors/1; event: cf9e7a70-1c17-11ef-89bf-005056afd35a] org.mule.runtime.core.privileged.processor.chain.AbstractMessageProcessorChain: Unexpected state. Error handler should be invoked with either an Event instance or a MessagingException
java.lang.OutOfMemoryError: GC overhead limit exceeded

1) Navigate to AFX/esb/conf folder

2) Update wrapper.conf to update the following lines    

# Initial Java Heap Size (in MB) -Xms
 wrapper.java.initmemory=4092
 
# Maximum Java Heap Size (in MB) -Xmx
 wrapper.java.maxmemory=4092

3) Restart AFX

Note: please note that the values above are for demonstration purposes only.

A more comprehensive set of values is mentioned in our documentation: RSA Governance & Lifecycle 8.0.0 Deploying Remote Collection Agent and Provisioning Service Guide | RSA Community on page: 15