Le 06/03/16 23:50, Shawn McKinney a écrit : >> On Mar 6, 2016, at 3:52 PM, Chris Pike <[email protected]> wrote: >> >> I'm guess I'm not following why the original code wasn't working. Ehcache is >> thread safe. > True, but that thread safety doesn’t cover the loading of the graph data > structure into memory. Including a server roundtrip and traversal of result > set into the digraph.
That's the pb. And the complex readWriteLock dance was an attempt to make it thread safe by allowing a thread to have read access when the graph already exists, but letting another thread updating the graph. The original version was using a syncrhonized section instead.
