There is a shutdown bug, where the keys don't get stored, that I'm going to try and get the fix in tomorrow. However, I've never heard of a deadlock problem.
Can you tell me two things: 1. Why do you think there is a locking problem with the indexed disk cache in particular and not somewhere else? That somewhere else should include the possibility of it being outside of JCS. 2. Are you using groups--the element group feature? And can you show me this warning you're talking about. And can you send your cache access code. Thanks, Aaron > -----Original Message----- > From: Corin Moss [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 10, 2004 4:00 AM > To: [EMAIL PROTECTED] > Subject: Deadlock in Indexed Disk Cache > > > Hi Guys, > > Thanks for all the work you've put into JCS, it's one of the best JSR-107 > implementations out there. Its completeness really is amazing :) > > I'm coming up against the deadlock problem within the Index disk cache. I > know several people have found this, but I'm not sure that anyone really > has a definitive answer regarding what causes it. > > I've seen a warning in the readLock method of the ReadWriteLock class > which warns against synchronizing calls, is this where the problem lies? > > I'm experiencing deadlock after about 30mins of heavy(ish) usage. > > I'd really like to continue using JCS, I'm helping with the effort across > at Cocoon - we're investigating JCS as a default store for Cocoon. I just > need to get a slightly better understanding of the issues remaining. > > On another note, has any thought been given to promoting JCS to a jakarta > level project (rather than a child of Turbine)? > > Any feedback on this issue, and the general state of JCS in heavy > production environments would be most appreciated. > > Thanks, > > Corin > > ================================================================ > CAUTION: This e-mail and any attachment(s) contains information > that is intended to be read only by the named recipient(s). It > may contain information that is confidential, proprietary or the > subject of legal privilege. This information is not to be used by > any other person and/or organisation. If you are not the intended > recipient, please advise us immediately and delete this e-mail > from your system. Do not use any information contained in it. > > ================================================================ > For more information on the Television New Zealand Group, visit > us online at http://www.tvnz.co.nz > ================================================================ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
