web server - Borland Technical Publications

EJB Container-level Properties
Table 31.1
EJB container properties (continued)
Property Description Default
ejb.cacheTimeout=
ejb.sfsb.aggressive_passivation=true|
false
ejb.sfsb.factory_name=
ejb.logging.verbose=true|false
ejb.logging.doFullExceptionLogging=true|
false
ejb.jss.pstore_location=
ejb.jdb.pstore_location=
This property hints the container to
invalidate the data fields of entity beans
after a specified time-out period. Use
the property by specifying the interval
for which the container will not load a
bean's state from the database, but
uses the cached state instead. At the
end of the expire period specified, the
container marks the bean as dirty (but
keeps its association with the primary
key), forcing the instance to load its
state from the database (not the cache)
before it can be used in any new
transactions. The property is expected
to be used by entity beans that are not
frequently modified.
The property is a positive integer
representing cache intervals in
seconds.
This is only valid for commit mode A. It
is ignored if specified for any other
commit mode.
If set to true, stateful session bean is
passivated no matter when it was used
last time. This enables fail-over support,
so if an EJB container fails, the session
can be restored from the last saved
state by one of EJB containers in the
cluster. If set to false, only the beans
which were not used since the last
passivation attempt, are passivated to
JSS. This makes the fail-over support
less deterministic, but speeds things up.
Use this setting, to trade performance
for high-availability.
If set, makes the stateful session beans
use a different JSS from the one that is
running within the same EJB container
or Partition. Specify the factory name of
JSS to use. This is the name under
which JSS is registered with Smart
Agent (osagent).
If set to true, the EJB container logs
messages about unexpected situations
which potentially could require user's
attention. The messages are marked
with >>>> EJB LOG