Support Article
File listener uses library function rule before engine starts
SA-67384
Summary
Error occurs when the file listener uses the library function rule before the engine starts.
Error Messages
[STANDARD] [ ] [ ] (tener.ListenerStateManagerImpl) ERROR - Caught exception while launching service listener CollectionBatch of type Data-Admin-Connect-FileListener
com.pega.pegarules.pub.runtime.IndeterminateConditionalException: ** Invalid expression or reference: No candidates found [possible function name, ruleset/version or number of parameter problem]
at com.pega.pegarules.priv.FUAUtil.activityPreTranIndeterminateConditionalCheck(FUAUtil.java:442)
at com.pegarules.generated.activity.ra_action_updateoperatorid_1ae11abed39a93a267b957dab5a99760.step1_circum0(ra_action_updateoperatorid_1ae11abed39a93a267b957dab5a99760.java:180)
>>> Engine is fully up at 2018-10-09 10:45:02,103
2018-10-09 10:45:02,103 [ STANDARD] [ ] [ ] (ervlet.WebAppLifeCycleListener) INFO - Web Tier initialization is complete.
Function rule referred in the 'updateOperatorID' OOTB activity is '@(Pega-RULES:String).equals(OperatorID.pyUserIdentifier, Primary.pyUserIdentifier)'
Steps to Reproduce
Not Applicable
Root Cause
A defect in Pegasystems’ code or rules.
There is no additional API to check if the application started completely. Hence, a new implementation is made to ensure if the node is started. Before the system started, the file listener started processing files and referenced the mAgent which is null from the error stack.
Resolution
Apply the following hotfixes:
- HFix-48050
- HFix-48014
Published January 17, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.