Sure, after looking at it some more, the cache values are being updated, so I'm going to test if we can just use the cache APIs locking methods.
----- Original Message ----- From: "Shawn McKinney" <[email protected]> To: [email protected] Sent: Friday, March 11, 2016 11:19:28 AM Subject: Re: LDAP Connection Management > On Mar 11, 2016, at 10:11 AM, Chris Pike <[email protected]> wrote: > > Found another place wehre this might be an issue... > > OrgUnitP and PolicyP both use read locks in the isValid method and write > locks in the add method, but only around getting user and policy sets > respectively. Also, it looks like PolicyP calls lock on read lock method > multiple times (isValid and getPolicySet). > > Since these are both also using a blocking cache, I think the locking is > unnecessary. Makes sense that we would fix these all now. Chris can you make the change to code? Shawn
