3 Replies Latest reply on Mar 26, 2012 1:09 PM by Paul Ferraro

    Multiple wars using session backed by FileCacheStore

    Michael Nielson Newbie

      I've got three wars in an ear all using a distributed infinispan cache. The cache configuration looks like this:

       

      <cache-container name="web" aliases="standard-session-cache" default-cache="http-session-local" start="EAGER">
           <transport lock-timeout="60000"/>
           <local-cache name="http-session-local" batching="true">
                <file-store/>
           </local-cache>
      </cache-container>
      

       

      One war is bound to the root context, the other two have their own context. The war that is bound to the root is logging warnings about unexpected files in the FileCacheStore:

       

      00:00:11,121 WARN  [org.infinispan.loaders.file.FileCacheStore] (Scheduled-eviction-thread-0) ISPN000163: FileCacheStore ignored an unexpected file diagnostics in path /jboss/domain/servers/server-one/data/web/default-host. The store path should be dedicated!

       

      The file diagnostics is created by the diagnostics war and the war bound to the root is trying to use the default-host directory as it's own.

       

      It seems as if this is a bug and the root context ought to have a cache with it's own directory. Maybe _ or ROOT.war, maybe the name of the war bound to root?

       

      Is there a workaround or fix for this? None of the attributes on <file-store/> seem to help.

       

      Michael

       

      I'd like to submit a patch or start a bug for this but I haven't found the correct touch point. It looks as if the touch point is in DistributedCacheManagerFactory but it appears that this is read in from a config and the standard config doesn't have this data?