Discussion

4
Replies
746
Views
PrabirKumarGhosh Member since 2012 1 post
Ness Technologies
Posted: 5 years ago
Last activity: 5 years 2 months ago
Closed

Rule resolution issue

Hi All,

          We are using Pega 7.1.5 and experiencing Pega rule resoution issue. Rule not found is reported while executing a flow but when we manually searched for the rule from developer portal, we can see the rule is present in class hierarchy and list of available rulesets for the logged-in user who is getting the rule not found error.

The same code is working fine in other environments.

In log we can see the below error. If anyone faced similar issue and resolved, appreciate your help.

01:01:11,700 [   PegaRULES-Batch-1] (l.vtable.VirtualRulesTableImpl) ERROR - VTable can't load rule resolution support

com.pega.pegarules.pub.database.BadInputException: This external handle is not valid: PLEASE SELECT VALID INPUT

From: (BF930BE63072BC2ED94180FBCD3418486)

        at com.pega.pegarules.data.internal.access.InstanceName.getKeysFromInsId(InstanceName.java:586)

        at com.pega.pegarules.data.internal.access.InstanceName.getKeysFromRuleInsKey(InstanceName.java:520)

        at com.pega.pegarules.data.internal.vtable.VirtualRulesTableImpl.getLoadQueryClasses(VirtualRulesTableImpl.java:509)

        at com.pega.pegarules.data.internal.vtable.VirtualRulesTableImpl.loadVirtualTable(VirtualRulesTableImpl.java:251)

        at com.pega.pegarules.data.internal.vtable.VirtualRulesTableImpl.noteChange(VirtualRulesTableImpl.java:1814)

        at com.pega.pegarules.data.internal.access.DatabaseImpl.removeFromNodeCache_(DatabaseImpl.java:8975)

        at com.pega.pegarules.data.internal.access.DatabaseImpl.processChanges(DatabaseImpl.java:9291)

        at com.pega.pegarules.data.internal.access.DatabaseImpl.processChangesFromPulse(DatabaseImpl.java:9038)

        at com.pegarules.generated.activity.ra_action_systempulse_a1462dda5b31f9ac9c168dc5d8498965.step1_circum0(ra_action_systempulse_a1462dda5b31f9ac9c168dc5d8498965.java:473)

        at com.pegarules.generated.activity.ra_action_systempulse_a1462dda5b31f9ac9c168dc5d8498965.perform(ra_action_systempulse_a1462dda5b31f9ac9c168dc5d8498965.java:69)

        at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3265)

        at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:721)

        at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:602)

        at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:884)

        at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1192)

        at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:930)

        at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:829)

        at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:617)

        at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991)

        at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532)

        at java.lang.Thread.run(Thread.java:722)

Moderation Team has archived post
Share this page LinkedIn