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
Key:
Applies to Java administrative console of Advanced Edition Version 4.0
Applies to Web administrative console of Advanced Single Server Edition Version 4.0
Applies to Application Client Resource Configuration Tool
-
Application Server
- The application server of which the EJB container is a part
-
Default Data Source
- The data source to use to connect to a JDBC-compliant database, such as DB2
-
Cache clean-up interval
or Clean-up Interval
- 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 specified
for cache size.
The cache manager tries to maintain some unallocated entries that can
be allocated quickly, 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.
For Advanced Single Server Edition: This value must be
a positive integer specified in milliseconds.
In the following XML configuration markup for the EJB container,
<cache-sweep-interval> represents the cache clean-up interval:
<cache-config>
<cache-size>2047</cache-size>
<cache-sweep-interval>1000</cache-sweep-interval>
<passivation-directory/>
</cache-config>
-
Cache size
- The number of buckets in the cache hash table.
The number of buckets in the cache hash table.
For efficiency, the EJB container actually uses the next prime number as cache size.
For example, if this is specified to be 2047, the container uses 2053.
For Advanced Single Server Edition: This value must be a positive integer.
-
Inactive Pool Cleanup Interval
- The interval at which inactive pools will be reduced to their minimum size.
For Advanced Single Server Edition: The value must
be a positive integer specified in milliseconds.
-
Installed EJB Modules
- The EJB modules that are installed in the EJB container of this server
-
Node
- The node with which the application server is associated
-
Passivation Directory
- The directory into which the container will save 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 step fails (for example, if the bean
instance is no longer in the passivation directory), then the method invocation fails.
|
|