AFX failure when Proxy is enabled without defining Proxy Host or Port values in RSA Governance & Lifecycle
Last Modified: 2024-02-09
Article Number
000071974
Applies To
This is a known issue in the following version:
  • RSA Governance & Lifecycle 8.0
Issue

The following log message is logged repeatedly in esb.AFX-MAIN.log:

ERROR 2023-12-20 10:21:52,211 [[MuleRuntime].uber.08: [10-AFX-MAIN].PRIMARY_REQUEST.BLOCKING @4038943d] [processor: PRIMARY_REQUEST/processors/5/route/0/processors/1; event: 972b2b72-9f21-11ee-81ec-060963f3a8f9] org.mule.runtime.core.internal.exception.OnErrorPropagateHandler: 
********************************************************************************
Message               : "Unable to convert '' with class 'java.lang.String' to class 'int'

A similar error shows in a very large number of log-batch-<hash>.xml log files under folder AFX/esb/logs/sent:

		Message               : &amp;quot;Unable to convert '' with class 'java.lang.String' to class 'int'

 

Cause
This issue occurs if the new "Proxy Enabled" feature of AFX Service is enabled but no Proxy Host or Proxy Port is provided.
Resolution

This issue is resolved in the following versions which now validates input when Proxy Enabled option is checked: 

  • RSA Governance & Lifecycle 8.0.0 P02
Workaround

Disable Proxy Enabled option for the AFX Server, or if the feature is enabled ensure you have valid values for Proxy Host and Proxy Port:

Image1.png

After saving the configuration, download the AFX Server archive from the UI and redeploy the AFX Server for the configuration changes to take effect.

Notes

Note that this is known to cause the following problem with AFX logging:
000071973 - Large volume of log files generated under AFX folder in RSA Governance & Lifecycle

Related Articles

Trending Articles

Don't see what you're looking for?