0 Replies Latest reply on Jul 4, 2013 3:46 PM by Louis-Félix Tessier

    "ISPN000151 : Error flushing to file" when closing cache manager

    Louis-Félix Tessier Newbie

      Hi,

       

      Sometime (I can not guess the exact cause), when I am closing the cache manager, I am getting this error for every file in the file cache store:

       

      2013-07-04 13:06:51,949 ERROR {Thread-0} [o.i.l.f.FileCacheStore:592] ISPN000151: Error flushing to file: sun.nio.ch.FileChannelImpl@232c15bc java.nio.channels.ClosedChannelException: null

              at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:88) ~[na:1.6.0_26]

              at sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:339) ~[na:1.6.0_26]

              at org.infinispan.loaders.file.FileCacheStore$BufferedFileSync.stop(FileCacheStore.java:590) ~[infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.loaders.file.FileCacheStore.stop(FileCacheStore.java:392) ~[infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.loaders.decorators.AbstractDelegatingStore.stop(AbstractDelegatingStore.java:160) ~[infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.loaders.decorators.AsyncStore.stop(AsyncStore.java:339) ~[infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.loaders.CacheLoaderManagerImpl.stop(CacheLoaderManagerImpl.java:298) [infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_26]

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_26]

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_26]

              at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_26]

              at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:205) [infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:889) [infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:694) [infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:572) [infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:246) [infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.CacheImpl.stop(CacheImpl.java:713) [infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.CacheImpl.stop(CacheImpl.java:708) [infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:731) [infinispan-core-5.3.0.Final.jar:5.3.0.Final]

              at ...

       

      Config:

      - Infinispan 5.2.5.Final or 5.3.0.Final

      - Linux  2.6.9-67.0.15.ELsmp x86_64

      - Java(TM) SE Runtime Environment (build 1.6.0_26-b03)

      - Jetty 8.1.11 embedded

       

      I am using 3 fileStore that all look like this (replication mode):

       


      <namedCache name="cache2">
          <loaders passivation="false" shared="false" preload="false">
            <fileStore
                    fetchPersistentState="true"
                    purgerThreads="1"
                    purgeSynchronously="true"
                    ignoreModifications="false"
                    purgeOnStartup="false"
                    location="/data/infinispan">
                <async
                    enabled="true"
                    flushLockTimeout="15000"
                    threadPoolSize="1" />
                <singletonStore
                    enabled="false"
                    pushStateWhenCoordinator="true"
                    pushStateTimeout="20000" />
            </fileStore>
          </loaders>

      </namedCache>

       

      Is it a known issue?

      Thanks!