Yes, this is a showstopper, our servers are getting hung up every few days, and this will prevent us from using the service in production.
Can you point me to where data is getting written in these methods? I'm only seeing reads. ----- Original Message ----- From: "Shawn McKinney" <[email protected]> To: [email protected] Sent: Sunday, March 6, 2016 2:37:54 PM Subject: Re: LDAP Connection Management > On Mar 6, 2016, at 1:08 PM, Chris Pike <[email protected]> wrote: > > I'm not an expert on concurrency, but I think the problem might be the code > trying to upgrade the read lock to a write lock... > > http://stackoverflow.com/questions/464784/java-reentrantreadwritelocks-how-to-safely-acquire-write-lock Similar, not an expert. This code has been reworked in the past couple of years and needs to be again. > On Mar 6, 2016, at 1:08 PM, Chris Pike <[email protected]> wrote: > > Stepping back for a second, what is the purpose of using the lock? Thread safety on the graph datastructs (hier role and orgs). There is potential for multiple threads accessing with reads and writes. This code has been rewritten some time ago and needs to be again apparently. I’ve opened a jira to cover the work. Question is this a showstopper? Shawn
