Support Article
Proposition data sync issue across production nodes
Summary
User is having Next Best Action Marketing (NBAM) 7.12 and Next-Best-Action Advisor (NBAA) 7.12 on Pega 7.1.7.
User has observed LibraryFunctionNotFoundException in NBO production nodes in pegarules log post deployment - addition of Propositions.
The same exception is occurring whenever there is a deletion or addition of Propositions . User when analysed could find that these exception are due to Proposition data not getting synchronized between the different nodes.
Pega articles suggests to add PegaDM:Administrators as access group for Pega:Rules Agent to make all node in sync.
When the user checked in PROD all active system nodes have PegaDM:Administrators added.
User wants to know what should be done to achieve this synchronization across all production nodes.
Error Messages
ERROR - java.lang.reflect.Method.pyHandlePulse(String,String,String,String)' threw this exception:
com.pega.pegarules.pub.runtime.LibraryFunctionNotFoundException: Failed to find instance 'pyHandlePulse--(String,String,String,String)' of type Rule-Utility-Function defined in 'pega_decisionengine_pulseextension'
at com.pega.pegarules.generation.internal.library.LibraryMetadataCache.getFunctionInstance(LibraryMetadataCache.java:334)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:124)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:110)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(Executable.java:8786)
at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflection(LibrarySupport.java:181)
Steps to Reproduce
1) Remove Propositions by running activity.
2) Add Propositions by deploying the jar that contains new Propositions.
3) Check individual nodes by logging in under Proposition Management page
Proposition data is visible in only few nodes. Post restart, it is working fine.
Root Cause
PegaDM:Administrators Access Group was not added for non-active nodes
Resolution
PegaDM:Administrators Access Group should be added to Pega-RULES:Core Engine Processing Agent data instances for all active and non-active nodes.
Published September 14, 2016 - 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.