Use this page to configure and manage a specific EJB container.
To view this administrative console page, click Servers > Application Servers > serverName > EJB Container.
Configuration tab
Beans are passivated when the number of active bean instances becomes greater than the cache size specified in the container configuration. When a stateful bean is passivated, the container serializes the bean instance to a file in the passivation directory and discards the instance from the bean cache. If, at a later time, a request arrives for the passivated bean instance, the container retrieves it from the passivation directory, deserializes it, returns it to the cache, and dispatches the request to it. If any step fails (for example, if the bean instance is no longer in the passivation directory), the method invocation fails.
For a cluster of servers that span multiple systems in a sysplex and have stateful session beans with an activation policy of Transaction deployed in them, the passivation directory must reside on a hierarchical file system (HFS) that is shared across the multiple systems.
Data type | Integer |
Units | Milliseconds |
Range | 0 to 2 147 483 674 |
Servlets and enterprise beans use data sources to obtain these connections. When configuring a container, you can specify a default data source for the container. This data source becomes the default data source used by any entity beans installed in the container that use container-managed persistence (CMP).
The default data source for a container is secure. When specifying it, you must provide a user ID and password for accessing the data source.
Specifying a default data source is optional if each CMP entity bean in the container has a data source specified in its configuration. If a default data source is not specified and a CMP entity bean is installed in the container without specifying a data source for that bean, applications cannot use that CMP entity bean.
Data type | String |
Default | Started |
Range | Valid values are Started and Stopped |