Change requests provisioned by AFX remain in "pending action" or "pending verification" in RSA Governance & Lifecycle
2 years ago
Article Number
000068307
Applies To

This is a known issue in the following versions:

  • SecurID Governance & Lifecycle 7.5.2
  • RSA Governance & Lifecycle 8.0
Issue

 Some change requests are not getting completed, even after their activities are all fulfilled in the end source and data collected back.

This results in the change request status showing "pending action" or "pending verification".

The message "Failed to invoke ScriptComponent" is logged in the AFX connector log:

        ********************************************************************************
        Message               : Failed to invoke ScriptComponent{AFX_OUT.component.1051028481}. Component that caused exception is: ScriptComponent{AFX_OUT.component.1051028481}. Message payload is of type: String
        Code                  : MULE_ERROR--2
        --------------------------------------------------------------------------------
        Exception stack is:
        1. null (java.lang.NullPointerException)
          java.util.Hashtable:460 (null)
        2. java.lang.NullPointerException (javax.script.ScriptException)
          org.codehaus.groovy.jsr223.GroovyScriptEngineImpl:323 (http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/script/ScriptException.html)
        3. Failed to invoke ScriptComponent{AFX_OUT.component.1051028481}. Component that caused exception is: ScriptComponent{AFX_OUT.component.1051028481}. Message payload is of type: String (org.mule.component.ComponentException)
          org.mule.component.AbstractComponent:144 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/component/ComponentException.html)
        --------------------------------------------------------------------------------
        Root Exception stack trace:
        java.lang.NullPointerException
            at java.util.Hashtable.put(Hashtable.java:460)
            at org.apache.log4j.MDC.put0(MDC.java:150)
            at org.apache.log4j.MDC.put(MDC.java:85)
            + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
        ********************************************************************************

 

Cause
In some instances an exception in AFX was preventing the outbound command mapping parameters from being set correctly. 
Resolution
This issue is resolved in the following versions which traps the exception that prevents outbound command mapping. 
  • SecurID Governance & Lifecycle 7.5.2 P09
  • RSA Governance & Lifecycle 8.0.0 P01