Database Connectors are failing when Command Output Parameters are configured in RSA Governance & Lifecycle
Originally Published: 2025-04-08
Last Modified: 2026-06-15
Article Number
Applies To
RSA Product Set: RSA Governance & Lifecycle
RSA Version/Condition: 8.0 GA- 8.0.0 P06 (inclusive)
Issue
Having "Command Output Parameters" active to map account.name in AFX for "Create an Account" fails with the below errors:
Logged in the esb.AFX-MAIN.log:
ERROR [MuleRuntime].uber.22: [10-AFX-MAIN].AFX_DO_FULFILLMENT_STATE.BLOCKING @45c59fa6] [processor: ; event: cbe578d0-0671-11f0-af3f-005056af6530] org.mule.runtime.core.privileged.exception.DefaultExceptionListener:
********************************************************************************
Message : "Cannot coerce Null to String
2| arg0 : vars.endpointId as String ,
^^^^^^^^^^^^^^^^^^^^^^^^^
Trace:
at anonymous::main (line: 2, column: 8)" evaluating expression: "{
arg0 : vars.endpointId as String ,
arg1 : vars.verbName as String ,
arg2 : vars.crId as String ,
arg3 : vars.messageId as String
}".
Element : AFX_DO_FULFILLMENT_STATE/processors/5 @ 10-AFX-MAIN:fulfillment-state-components.xml:126 (Invoke SetFulfillmentLogContext)
Element DSL : <java:invoke doc:name="Invoke SetFulfillmentLogContext" doc:id="fb62b552-fa9c-44f7-98cb-452e95088033" instance="#[vars.fulfillmentLogContextInst]" class="com.aveksa.afx.server.log.context.FulfillmentLogContext" method="setFulfillmentLogContextValues(java.lang.String, java.lang.String, java.lang.String, java.lang.String)" target="fulfillmentLogSet">
<java:args><![CDATA[
#[{
arg0 : vars.endpointId as String ,
arg1 : vars.verbName as String ,
arg2 : vars.crId as String ,
arg3 : vars.messageId as String
}]
]]></java:args>
</java:invoke>
Error type : MULE:EXPRESSION
FlowStack : at AFX_DO_FULFILLMENT_STATE(AFX_DO_FULFILLMENT_STATE/processors/5 @ 10-AFX-MAIN:fulfillment-state-components.xml:126 (Invoke SetFulfillmentLogContext))
at AFX_JMS_FULFILLMENT_STATE_RETRY(AFX_JMS_FULFILLMENT_STATE_RETRY/processors/4 @ 10-AFX-MAIN:fulfillment-state-components.xml:110 (Flow Reference))
at AFX_JMS_FULFILLMENT_STATE(AFX_JMS_FULFILLMENT_STATE/processors/15/route/0/processors/1 @ 10-AFX-MAIN:fulfillment-state-components.xml:90 (Flow Reference))
(set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
********************************************************************************
Logged in the connector's log:
ERROR [MuleRuntime].uber.22: [AFX-CONN-MSSQL_Sanity_Check].AFX-CONN-MSSQL_Sanity_CheckOutputParameter.BLOCKING @25606778] [processor: AFX-CONN-MSSQL_Sanity_CheckOutputParameter/processors/2/processors/1/route/0/processors/0; event: cbe578d0-0671-11f0-af3f-005056af6530] org.mule.runtime.core.privileged.exception.DefaultExceptionListener:
********************************************************************************
Message : Couldn't find class: com.aveksa.DbUtils
Element : AFX-CONN-MSSQL_Sanity_CheckOutputParameter/processors/2/processors/1/route/0/processors/0 @ AFX-CONN-MSSQL_Sanity_Check:AFX-CONN-MSSQL_Sanity_Check.xml:628 (replacePlaceHolder)
Element DSL : <java:invoke doc:name="replacePlaceHolder" doc:id="be3d0d16-3a03-40eb-9eeb-0340a4354331" class="com.aveksa.DbUtils " instance="#[vars.DbUtilsObj]" method="replacePlaceHolder(java.lang.String)" target="outputParamQuery">
<java:args><![CDATA[
#[output application/java
---
{
arg0: vars.paramQueryMap[0].query
}]
]]></java:args>
</java:invoke>
Error type : JAVA:CLASS_NOT_FOUND
FlowStack : at AFX-CONN-MSSQL_Sanity_CheckOutputParameter(AFX-CONN-MSSQL_Sanity_CheckOutputParameter/processors/2/processors/1/route/0/processors/0 @ AFX-CONN-MSSQL_Sanity_Check:AFX-CONN-MSSQL_Sanity_Check.xml:628 (replacePlaceHolder))
at AFX-CONN-MSSQL_Sanity_CheckFlow(AFX-CONN-MSSQL_Sanity_CheckFlow/processors/22/route/2/processors/4/route/0/processors/1 @ AFX-CONN-MSSQL_Sanity_Check:AFX-CONN-MSSQL_Sanity_Check.xml:256 (AFX-CONN-MSSQL_Sanity_CheckOutputParameter))
(set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
******************************************************************************** Resolution
This issue is resolved in the following versions:
- RSA Governance & Lifecycle 8.0.0 P07 and later versions/ patches.
Related Articles
Data Collections fail with 'An invalid XML character (Unicode: 0x0) was found in the element content of the document' / 'I… 258Number of Views Change Verification step runs for hours in RSA Identity Governance & Lifecycle 59Number of Views Cisco FTD - RSASecurID Access Implementation Guide 71Number of Views The Active Directory Account Data Collector does not have an option to collect Logon Hours in RSA Identity Governance & Li… 54Number of Views Installation of RSA Identity Governance & Lifecycle 7.0.2 fails during WildFly install/config phase with jboss-modules.jar… 136Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA Authentication Manager Patch Updates How to factory reset an RSA Authentication Manager 8.x hardware appliance without a factory reset button from the Operatio… Determine SUSE Linux version from the command line in RSA Authentication Manager 8.x
Don't see what you're looking for?