James, On one of the test runs I did to reproduce the other issues in LRUMemoryCache, I was able to identify a potential sychronization error that could be the result of lack of synchronization in this method.
By sync'ng this method, and the other fixes, I was able to eliminate the problems that we were seeing. It is possible that this sync' is unnecessary, as it may have been masked by one of the other issues that has now been fixed. I will be doing a lot of stress testing and will disable sync'ng of this method and see if we see any further issues. Todd Enersen [EMAIL PROTECTED] -----Original Message----- From: James Taylor [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 11, 2003 1:24 PM To: [EMAIL PROTECTED] Subject: Re: cvs commit:jakarta-turbine-jcs/src/java/org/apache/jcs/engine/memory/lruLRUM emoryCache.java > get(): Synchronizing method to prevent possible issues. > Adding debug code to verify cache after method completion. Isn't this going to slow things down? Not sure what the possible issues are but one of the reasons this class is so complex is to allow get to be not synchronized. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
