Configuring Passivation

You can enable and disable passivation for stateful session beans using the server.xml file (see "Using Deployment XML").

You may choose to disable passivation for any of the following reasons:

• Incompatible object types: if you cannot represent the nontransient attributes of your stateful session bean with object types supported by passivation (see "What Object Types can be Passivated?"), you can exchange increased memory consumption for the use of other object types by disabling passivation.

• Performance: if you determine that passivation is a performance problem in your application, you can exchange increased memory consumption for improved performance by disabling passivation.

• Secondary storage limitations: if you cannot provide sufficient secondary storage (see "Configuring Passivation Location"), you can exchange increased memory consumption for reduced secondary storage requirements by disabling passivation.

For more information, see the following:

• "When Does Stateful Session Bean Passivation Occur?"

• "Configuring Passivation Criteria"

• "Configuring Passivation Location"

Using Deployment XML

For an EJB 3.0 stateful session bean, you configure passivation in the server.xml file as you would for an EJB 2.1 stateful session bean (see "Using Deployment XML").