Red Hat Application Server, Руководство пользователя

Страница: 126 / 296

118 Chapter 8. Developing Entity Beans
8.12.7. passivation-timeout
Entity Bean instances are passivated at the end of the transaction and reactivated at the beginning of
the next transaction. In the event that these instances are accessed outside a transaction, their state is
kept in memory to improve performance. However, a passivation will occur in three situations:
•
When the bean is unloaded from the server, at a minimum when the server is stopped.
•
When a transaction is started on this instance.
•
After a configurable timeout. If the bean is always accessed with no transaction, it may be prudent
to periodically store the bean state on disk.
This passivation timeout can be configured in the JOnAS-specific deployment descriptor, with a non-
mandatory tag
n
passivation-timeout
o
.
p
jonas-entity
q
p
ejb-name
q
Item
p
/ejb-name
q
p
passivation-timeout
q
5
p
/passivation-timeout
q
.....
p
/jonas-entity
q
Example 8-1. Passivation timeout
This Entity Bean will be passivated every five second, if not accessed within transactions.