+

Search Tips   |   Advanced Search

Example: Read-read consistency checking


Read-read consistency checking only applies to LifeTimeInCache beans whose data is read from another transaction.

 

Usage scenario

For the access intents that are for repeatable read (RR), this means WAS checks that the data is consistent with that in the data store and ensures that no one updates it after the checking. For the Access Intents that are for read committed (RC), this means WAS checks that the data is consistent at the point of checking, but it does not guarantee that the data does not change after the checking. This makes the behavior of the LifeTimeInCache bean the same as non-LifeTimeInCache beans.

we have three options for setting consistency checking, as shown in the following scenarios concerning the calculation of interest in "Ann's" bank account. In each case, the data store is shared by this EJBs container managed persistence (CMP) application to calculate the interest and other applications, such as EJB bean managed persistence (BMP) , JDBC, or legacy applications. Also in each case, the EJB account is configured as a long-lifetime bean.

 

NONE

 

Read-read checking AT_TRAN_BEGIN

 

Read-read checking AT_TRAN_END





Related concepts


Enterprise beans
Concurrency control

 

Related tasks


Develop applications that use JNDI

 

Related


WebSphere extensions to the Enterprise Java Beans specification
Enterprise bean development best practices