[ http://jira.jboss.com/jira/browse/JBCACHE-807?page=all ] Manik Surtani updated JBCACHE-807: ---------------------------------- Fix Version/s: 2.0.0.CR1 Assignee: Manik Surtani (was: Brian Stansberry) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBCACHE-807?page=comments#action_12357955 ] Manik Surtani commented on JBCACHE-807: --------------------------------------- As a potential section under file cache loaders in the user guide, FCL javadoc and an FAQ: "The FileCacheLoader has some severe limitations which restrict it's use in a production environment, or if used in such an environment, it should be used with due care and sufficient understanding of these limitations. * Due to the way the FileCacheLoader represents a tree structure on disk (directories and files) traversal is inefficient for deep trees. * Usage on shared filesystems like NFS, Windows shares, etc. should be avoided as these do not implement proper file locking and can cause data corruption. * Usage with an isolation level of NONE can cause corrupt writes as multiple threads attempt to write to the same file. * File systems are inherently not transactional, so when attempting to use your cache in a transactional context, failures when writing to the file (which happens during the commit phase) cannot be recovered. As a rule of thumb, it is recommended that the FileCacheLoader not be used in a highly concurrent, transactional or stressful environment, and it's use is restricted to testing." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira