The Session Store Location field specifies the directory where passivated beans and persisted HTTP sessions are stored on the file system.
Passivated beans are enterprise beans that have had their state written to a file on the file system. Passivated beans typically have been idle for a certain period of time, and are not currently being accessed by clients. Similarly, persisted HTTP sessions are individual web sessions that have had their state written to a file on the file system.
The Commit Option field specifies how the container caches passivated entity bean instances between transactions.
Option B caches entity bean instances between transactions, and is selected by default. Option C disables caching.
Increase the maximum number of beans to cache to eliminate the overhead of bean creation and destruction. However, if the cache is increased, the server consumes more memory and resources. Be sure your operating environment is sufficient for your cache settings.
When the maximum number of cached beans is reached, the container removes a number of passivated beans from the backup store, set to 32 by default.
The container decides which stateful session beans to remove based on the policy set in the Removal Selection Policy field. There are three possible policies the container uses to remove beans from the cache:
Not recently used (NRU)
First in, first out (FIFO)
Least recently used (LRU)
The NRU policy removes a bean that hasn’t been used recently. The FIFO policy removes the oldest bean in the cache. The LRU policy removes the least recently accessed bean. By default, the NRU policy is used by the container.
Entity beans are always removed using the FIFO policy.
If a cached entity bean has been idle a certain amount of time, it is passivated. That is, the bean’s state is written to a backup store.