user manual

Chapter 13: Caching of Stateful Session Beans 127
Chapter
13
Chapter 13Caching of Stateful Session
Beans
The EJB Container supports stateful session enterprise beans using a high-
performance caching architecture based on the Java Session Service (JSS).
There are two pools of objects: the ready pool and the passive pool.
Enterprise beans transition from the ready pool to the passive pool after a
configurable timeout. Transitioning an enterprise bean to the passive pool
stores the enterprise bean's state in a database. Passivation of stateful
sessions exists for two purposes:
1 Maximize memory resources
2 Implement failover
Configuring Borland's JSS implementation (including the setting of properties)
is discussed in Chapter 6, “Java Session Service (JSS) configuration”. This
document explains the use of the properties that control the passivation and
persistence of individual session objects.
Important For documentation updates, go to www.borland.com/techpubs/bes.
Passivating Session Beans
At deployment time, the deployer uses the Borland Enterprise Server's tools to
set a passivation timeout for the EJB Container in a particular Partition. The
container regularly polls active session beans to determine when they are last
accessed. If a session bean has not been accessed during the timeout period,