I must agree with Matthew on the "perceived" status of the project. I also assumed it was a production release, definetely not Beta.
-----Original Message----- From: Matthew Cooke [mailto:[EMAIL PROTECTED] Sent: Tuesday, 27 April, 2004 16:12 To: Turbine JCS Users List Subject: Re: Additional problems. Aaron, * LTCP As recommended I replaced the keys with string keys and the LTCP out of order bug still occured. (we put in some monitoring and safeguards to catch any values that didn't match keys) before they were served. It seemed the problem was occured after restarting a server - and even with these simple string keys. Also these keys were used previously with another cache and are still being used with the current JCS branch (without LTCP) and aren't causing us any problems. I was unable to reproduce the bug in a low load enviroment but I didn't have time to try an automate solution. Trying to replicate the the 1000+ gets/sec and 30+ puts/sec with a broad load (eg, a large key set) is quite difficult even with automated tools - otherwise I would have tried to produce a rerunnable test case. If you have any idea how to quickly rerun a very broad load eg, a large key set quickly from multiple machines then I'll give it a try. It might require quite a bit of work. * Memory I will diff the JCS code I am currently using with the CVS version before reporting back any findings on the memory problems I am occuring and I'll make sure the problem isn't occuring outside of the code that is currently in CVS. I have increased the memory capacity on our server and given JCS remote cache 800MB in an attempt to delay further problems until I can profile it. --- By random patches I mean't patches that have yet to be applied to the JCS CVS version or indeed might not be applied to the CVS version. Once a patch has been applied to the CVS version I would no longer refer to it as random :) I appologise for the mistake regarding the release status of JCS I thought it was released as part of the turbine project and also worked stand alone. Because of this I assume it was released, stable and in use in turbine based projects. Perhaps describing the project status as Beta on the website might make this clearer to others. Matt. --------------------------------------------------------------------- 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]
