[infinispan-issues] [JBoss JIRA] (ISPN-3647) GridFileSystem data becomes corrupted if file-store evication is enabled.

GridFileSystem data becomes corrupted if file-store evication is enabled. ------------------------------------------------------------------------- Key: ISPN-3647 URL: https://issues.jboss.org/browse/ISPN-3647 Project: Infinispan Issue Type: Bug Components: Core API, Eviction Affects Versions: 5.2.6.Final Reporter: Lincoln Baxter III Assignee: Mircea Markus I don't know if this is still an issue or not in the 6.x branch, but this is occurring when using the Infinispan 5.2.6 provided with EAP6.1.1 (Yes, yes, I know you should not use the provided infinispan, but it's the easiest way to get it clustered on openshift.) This is my configuration: {code} <cache-container name="redoculous" aliases="ha-partition" default-cache="default" jndi-name="java:jboss/infinispan/redoculous-cluster"> <transport/> <replicated-cache name="filesystem.metadata" mode="SYNC" start="LAZY"> <locking isolation="REPEATABLE_READ"/> <eviction strategy="LIRS" max-entries="1000"/> <file-store path="redoculous" preload="true" passivation="true"/> </replicated-cache> <distributed-cache name="filesystem.content" owners="2" mode="SYNC" start="LAZY"> <locking isolation="REPEATABLE_READ"/> <eviction strategy="LIRS" max-entries="10000"/> <file-store path="redoculous" preload="true" passivation="true"/> </distributed-cache> </cache-container> {code} This is revealed particularly when pushing zip files to the grid. After retrieving them, upon attempt to decompress the file, ZipEntry will typically throw Exceptions about invalid entry header information, and various other sporadic issues. I believe this is an eviction issue because typically the first few files work, but things begin to fail more and more, the more files are placed into the grid filesystem.