On 7 April 2014 18:39, Thomas Vandahl <t...@apache.org> wrote: > On 04.04.14 02:32, sebb wrote: >> The FileDiskCacheUnitTest was failing because the tests were dependent >> on the file timestamp resolution, so the cache did not always treat >> the first created file as the oldest. >> Adding pauses as necessary fixed this. > > I inherited the code.
I don't think any of the original developers are still around. > Personally, I'd throw this type of cache away as I > don't see a real use case. It relies too much on the behavior of the > file system. Indeed. It also has some peculiar behaviour in that it allows the storage directory to be changed after initialisation. Looks like the directory can be anywhere so it might use a directory with existing files in it that are not actually cache files. Seems rather dangerous to allow this. >> I'm still trying to solve problems with BasicRemoteCacheClientServerUnitTest. >> It looks like the cache updates are not getting propagated to the server. > > Well, based on the log output of Continuum it looks like the client > tries to connect to the server before the server is up. I see lots of > "connection refused" exceptions in the log. Does the Continuum system > have problems with DNS/Reverse DNS or other network-related woes? No idea, but I suppose that's possible. > Bye, Thomas. > > PS: Thanks for looking into the code. It helps a lot. I thought it was going to be a lot easier than it has turned out to be. The code needs a lot of TLC to bring it up to date and make it thread-safe. > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
