Support Article
UnresolvedAssemblyError:Rule resolution multiple versions error
SA-19083
Summary
Errors appear sporadically in the logs regarding, UnresolvedAssemblyError: Rule resolution identified multiple versions of the rule with class.
Error Messages
com.pega.pegarules.pub.generator.UnresolvedAssemblyError: Rule resolution identified 3 versions of the rule with class Rule-Obj-Activity and name ClassName!ActivityName
at com.pega.pegarules.generation.internal.vtable.VirtualRuleTableDispatchImpl.useRuleResolutionToSelectRule(VirtualRuleTableDispatchImpl.java:765)
at com.pega.pegarules.generation.internal.vtable.VirtualRuleTableDispatchImpl.resolveRule(VirtualRuleTableDispatchImpl.java:455)
at com.pega.pegarules.generation.internal.PRGenProviderImpl.get(PRGenProviderImpl.java:586)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3260)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10274)
Steps to Reproduce
There is no specific use case to replicate this behavior.
Root Cause
A defect or configuration issue in the operating environment.
Resolution
Perform the following local-change:
- Set dynamic system setting, systempulse/scanoffsetms, to 60000 or 30000.
- Reassemble virtual table cache for affected rules.
- Open the System Management Application.
- Open the node experiencing the issue.
- Expand the Advanced menu.
- Select the Virtual Rule Table Cache Management landing page.
- Type the rule type class followed by a colon and the rule pxInsId.
- Click the button to get cache detail on the typed in rule.
- Click the button to reassemble cache for the rules captured from the cache detail search.
- Attempt the error case to confirm resolution. Navigate to System Management Application > Advanced Area, to reassemble the identified activity.
Published January 30, 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.