6 Replies Latest reply on Oct 1, 2007 6:28 AM by Manik Surtani

    Tracking whether nodes are in-memory vs persisted

    Brian Stansberry Master

      In 2.0 I don't see any way to determine whether a node exists in memory vs is passivated. In 1.x you can deduce this kind of thing by calling getChildrenNames() on the parent and then invoking exists() on the children. There's no equivalent API in 2.0.

      This is a problem with session passivation, where the session manager is controlling evictions. It needs to know how many sessions are in memory so it can decide whether to passivate sessions or allow creation of new ones. I can track cache changes easily enough after the manager starts, but I have no way to readily determine the initial state of things when a new node joins an already running cluster.

      Any ideas?