-
Bug
-
Resolution: Done
-
Medium
-
Frankfurt Release, Guilin Release
-
None
-
Any OOM installation
-
Policy 9/16-9/30, Policy 10/1 - 10/15
Issue
During testing it was found that CDS actor doesn't use the timeout defined in the operational policy. Rather it defines its own timeout using CdsServerProperties which is per PDP instance level (in case of drools-pdp) and not per policy level.
Solution
Update CDS actor to use the timeout configured in operational policy.
- mentioned in
-
Page Loading...