3 Replies Latest reply on Jun 14, 2010 10:42 PM by girishadat

    Internal FQN removal

    girishadat

      I tried attaching a single string object to PojoCache and detached it later. But even after detaching the object from cache, when monitored through JConsole, I noticed the internal fqn is still there in the cache.

      Why this reference is still maintained? When will it get removed?

      Thanks,
      Girish Adat

        • 1. Re: Internal FQN removal
          girishadat

          For more clarity for my query,

          # Content when cache is started

          / null


          # Content when an object is attached to PojoCache [fqn is "/z/0"]
          / null
           /z null
           /0 {PojoCache.LOCK,PojoCache.PojoReference}
           /__JBossInternal__ null
           /0 null
           /__ID__ null
           /<some hash> {PojoCache.PojoInstance,PojoCache.Status}


          # Content when the object is detached from PojoCache
          / null
           /z null
           /__JBossInternal__ null
           /0 null
           /__ID__ null


          I am using PojoCache 3.0.0 GA (with CoreCache 3.0.3 GA).

          My question is, why we have to maintain the third entry after detaching the object? Will it consume lots of memory when a large number of objects are attached and detached? Please advise.

          Thanks in advance,
          Girish Adat

          • 2. Re: Internal FQN removal
            ajuba

            same problem with me

            • 3. Re: Internal FQN removal
              girishadat

              Please visit : https://community.jboss.org/message/3192 and https://jira.jboss.org/browse/PCACHE-85.

               

              The work around is to call core cache APIs.

               

              i.e. pojoCache.getCache().removeNode("fqn")

               

              Hope this helps. Be careful @ making use of transactions directly.