Question
Hawaii Medical Service Association
US
Last activity: 17 Aug 2016 7:33 EDT
Rule Cache Disabled
Why is rule cache being disabled when i start the agent to run bix? What are the solutions?
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Pegasystems Inc.
IN
Upon reviewing the corresponding SR, we see that it has been resolved. SA-26806 was created as a result of the investigation. Please reference that if you have the same question.
Regards,
Lochan | Online Community Moderator | Pegasystems Inc.
Hi Gyan,
Can you explain where / how you are seeing that the rule cache is being disabled?
In addition, I believe you're using Pega 7.1.9, is that correct?
Hawaii Medical Service Association
US
Hi Nicholas,
I first noticed it in AES. And confirmed it in SMA as '
Cache Enabled | False |
and enabled it by going there manually. Every the BIX agent is started, this issue occurs. Please let me know if you need additional information.
Hi Gyan,
I was able to reproduce this by having an agent run that calls pxExtractDataWithArgs. It looks as if it did turn off Rule Caching (SMA > Advanced > Rule Cache Management).
It seems you may have found a bug, but it's possible this is expected for some reason. Hopefully someone more directly connected to the code can explain this behavior and or confirm that this is a bug.
Pegasystems Inc.
US
that is expected, see this link: I get an AES Alert that rule cache enabled false, how to enable the rule cache? The code snippet from ExtractImpl:
getData().getCacheContainer().disable();
Hawaii Medical Service Association
US
Hi Kevin,
Thank you for the additional information. I am willing to explore if there is a way to not disable it. If it must be disabled, if there is a way to enable automatically.
Pegasystems Inc.
US
Sorry I missed that you are running BIX from an agent, but not from command line. If you run BIX from command line, there is an enable call in the finally block.
cacheContainer.enable();
after extract is done. Your current scenario is a different execution path. It appears to be missing enable call after extract is done. Yes, it does look like an oversight to me. Once this is confirmed by SME, you should go head with a SR.
Hawaii Medical Service Association
US
Hi Kevin,
Thank you for your email. Would you please elaborate the effect of cache disabled? It seems that the cache is disabled on a node in which BIX agent run? Trying to think of some options at the moment: What will be an impact on performance when the BIX agent runs on a separate node dedicated to the running of BIX, and the cache is disabled all the time. No users would be routed to the node. Does the disable of rule cache on a bix node have any other impact for bix agent itself or other users or nodes?
ASB
NZ
I have the same issue in 7.19. Was an SR raised for this? Is there a hotfix?
Updated: 8 Aug 2016 17:24 EDT
BizArch Solutions Inc
US
We are running into same issue. If you have any solution from Pega please keep us informed.
Hawaii Medical Service Association
US
Hi Matthew,
We used separate node for bix and did not further my search.
Accepted Solution
Pegasystems Inc.
IN
Upon reviewing the corresponding SR, we see that it has been resolved. SA-26806 was created as a result of the investigation. Please reference that if you have the same question.
Regards,
Lochan | Online Community Moderator | Pegasystems Inc.