Thomas Vandahl commented on JCS-101:
Well, as the code has been working for almost two years and the compiled classes usually have no tendency to modify themselves, I guess something else changed in your environment.
You could try to use the current trunk on a test or staging system to see if things improve.
> Basic cache functions (store/delete) not occurring consistently
> Key: JCS-101
> URL: https://issues.apache.org/jira/browse/JCS-101 > Project: Commons JCS
> Issue Type: Question
> Components: Composite Cache
> Affects Versions: jcs-1.3
> Environment: Linux, running on VM
> Reporter: Mike Ellis
> Priority: Minor
> Our process had been deployed and running since December 2010 with no problems but two weeks ago we started seeing that updates were not working consistently, but we were not getting errors indicating any problems. We are using version 1.3
> Our setup specifies a primary and failover linux server - see cache.ccf snip below - but we see the error even when just one server is active. Separate domain restarts (we use VMs) did not resolve the issue. A simultaneous restart appeared to work (existing records gone, updates happened) but the problem reoccurred within hours.
> Commands like clear and dispose also failed to work. Normal ShrinkerThread tasks were running as expected.
> Our tech support are checking that the VM environment is working correctly, but is there a reason why store/delete/clear/dispose would not work and would not display an error?
> Also, is there a way to retrieve all existing keys from a region at runtime, rather than setting up a group and using putInGroup(...) as records are created? The aim is to retrieve the keys from every record in a specified region without changing code to specify/use groups.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira