InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.4: Administering EJB containers (overview) >
6.6.4.0: EJB container properties

6.6.4.0: EJB container properties

Cache absolute limit
Specifies the maximum number of bean instances permitted in the cache by the container cache manager. The container will fail to allocate new bean instances when the total number of active beans reaches this limit.

This value must be a positive integer.

Cache clean-up interval
Specifies the interval at which the container attempts to remove unused items from the cache to reduce the total number of items in the cache to the value of the Cache preferred limit property.

The cache manager tries to maintain some unallocated entries that can be quickly allocated as needed. A background thread attempts to free some entries while ensuring that some unallocated entries are maintained. If the thread runs while the application server is idle, then when the application server needs to allocate new cache entries, it does not pay the performance cost of removing entries from the cache.

In general, increase this parameter as the cache size increases.

This value must be a positive integer specified in milliseconds.

Cache preferred limit
Specifies a soft limit for the number of bean instances the container attempts to retain in the cache. The cache manager will use this value as a trigger to start discarding unused entries from the cache. See the cache clean-up interval description for details about the cleanup mechanism.

If necessary, the number of enterprise bean instances in the cache can increase to the value specified by the Cache absolute limit property. The difference between the Cache preferred limit and the Cache absolute limit can be thought of as the "surge capacity" for the container -- that is, the ability of the container to handle a spike in requests without having to passivate beans.

This value must be an integer less than or equal to the value of the Cache absolute limit.

Cache size
Specifies the number of buckets in the cache hash table.

If you change this value, change the Cache absolute limit property to correspond. For example, if you change the cache size to 3000, change the cache absolute limit to 3000, unless for some reason you do not want all of the available cache to be used.

This value must be a positive integer.

Current State
Indicates the state the container is currently in. The next time it is started, it will try to change to its desired state setting.
Data Source
Specifies the data source the container should use for the purpose of enterprise bean persistence.

Data Source in use
Specifies the data source currently in use.

Desired state
Indicates the state the container should have the next time it is started.
EJB Container name
Specifies a name for the container. The name must be unique within the application server that contains it.

Name
Indicates the name of the container

Passivation directory
Specifies the name of a directory where the container saves the persistent state of passivated session beans.

Session beans are passivated when the container needs to reclaim space in the bean cache. At passivation time, 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 of these steps fail (for example, if the bean instance is no longer in the passivation directory), then the method invocation fails.

Password
Specifies the password for accessing the container's data source.
Start time
Indicates the time at which the container was most recently started.

State
Indicates the state the container is currently in. The next time it is started, it will try to change to its desired state setting.
User ID
Specifies the user ID for accessing the container's data source.
User ID in use
Specifies the user ID currently in use.
Go to previous article: Administering EJB containers (overview) Go to next article: Administering enterprise bean containers with the Java administrative console

 

 
Go to previous article: Administering EJB containers (overview) Go to next article: Administering enterprise bean containers with the Java administrative console