user manual

Chapter 16: Using BES Properties for CMP 2.x 173
Setting Properties
These properties are for CMP 2.x implementations only:
ejb.maxBeans
InTransactio
ns
lava.lang.Integer 500*
see
Description
A transaction can access any/large
number of entities. This property sets
an upper limit on the number of
physical bean instances that EJB
container will create. Irrespective of
the number of database entities/rows
accessed, the container will manage
to complete the transaction with a
smaller number of entity objects
(dispatchers). The default for this is
calculated as ejb.maxBeansInCache/2. If
the ejb.maxBeansInCache property is not
set, this translates to 500.
ejb.Transact
ionCommitMod
e
Enumerated Shared Indicates the disposition of an entity
bean with respect to a transaction.
Acceptable values are:
Exclusive: This entity has exclusive
access to the particular table in the
database. The state of the bean at the
end of the last committed transaction
can be assumed to be the state of the
bean at the beginning of the next
transaction.
Shared: This entity shares access to
the particular table in the database.
However, for performance reasons, a
particular bean remains associated
with a particular primary key between
transactions to avoid extraneous calls
to ejbActivate() and ejbPassivate()
between transactions. The bean stays
in the active pool.
None: This entity shares access to the
particular table in the database. A
particular bean does not remain
associated with a particular primary
key between transactions, but goes
back to the ready pool after every
transaction.
Property Type Default Description
ejb.invalidateFinde
rCollectionAtCommit
java.lang.Boolean False Whether or not to optimize
transaction commit by
invalidating finder collections.
CMP 2.x only.
ejb.cacheCreate java.lang.Boolean True Whether or not to attempt to
cache the insert of the entity
bean until the ejbPostCreate is
processed.
Property Type Default Description