Use XACML Decision Caching with Correctness flag enabled
By default, the decision caching implementation uses a Least Recently Used LinkedHashMap implementation from the JDK. But many a times, if you are running in a system such as the JBoss Application Server or JavaEE containers, it may happen that there may rare classloader leaks etc. In those situations, you may want to bring in correctness to the decision caching. The correctness approach uses a WeakHashMap which is almost useless in a low transaction system as the JDK GC process cleans up the cache keys.  As mentioned in the Design Considerations section, this particular configuration will always yield the right results under dynamic conditions. The negatives of this approach include extended time (compared to the speed approach).            test/policies/interop/xacml-policySet.xml              test/policies/interop/xacml-policy2.xml                        test/policies/interop/xacml-policy3.xml                   test/policies/interop/xacml-policy4.xml                        test/policies/interop/xacml-policy5.xml                             urn:oasis:names:tc:xacml:1.0:environment:current-time        false    Â