History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CACHE-44
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Chris Miller
Reporter: Vipul Agarwal
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
OSCache

Multi threading issues with LRU Cache

Created: 18/Jun/03 12:56 PM   Updated: 14/May/06 08:50 AM
Component/s: Base Classes
Affects Version/s: 1.7.5
Fix Version/s: 2.0.2

Environment: SunOS 5.8
Issue Links:
Duplicate
This issue duplicates:
CACHE-39 LRUCache has multi-threading issues Major Closed
 
Related
This issue relates to:
CACHE-246 java.util.NoSuchElementException duri... Major Closed
 


 Description  « Hide
We are facing the same issue as CACHE-39, wherein multithreading issues with the LRU cache brings one of our weblogic servers in the cluster to a stand still. This server suddenly starts taking 80% cpu, and looking at the bug trace for CACHE-39 I can understand why it is doing that. Now this issue seems to be fixed and closed. Can somebody please let me know that if we have either of these things available:

1) A release after 1.7.5 that we can download, which has this bug fixed in it(Bug trace says the fix is in release 2.0, which is not available on the site).
2) Any kind of plugin code or something that fixes this bug and which we can hook into our existing release 1.7.5
3) Any kind of source code available or any suggestions for the code changes that we can make to fix this issue in release 1.7.5

This issue is significantly gating the performance of our application. A prompt help will be sincerely appreciated. Thanks in advance.

 All   Comments   Change History      Sort Order:
Chris Miller - [18/Jun/03 01:18 PM ]
You can either:
- use the current CVS version of OSCache (it will become the 2.0.0 release).
- or just apply Jean-Philippe's fix to the 1.7.5 codebase, as described in CACHE-39.

It would help us if you could use the OSCache mailing list for these kinds of problems in the future. You can sign up to the mailing list at http://sourceforge.net/mail/?group_id=9890.

Cheers,
Chris

Chris Miller - [28/Nov/03 09:30 AM ]
The suggested fix didn't completely solve the problem

Chris Miller - [28/Nov/03 09:31 AM ]
I had to add a little more synchronization. The original fix worked well for most cases, however when under extreme load (more threads than cache entries?) there was still a concurrency problem.