What is Read Committed?

In this isolation level, multiple instances of beans are created for each concurrent transaction. At the time of committing the transaction, the bean's container-managed fields are compared and an update is done only if the state is dirty.

Use Case Scenario

This option is used when the concurrent transactions are high in reads and low in updates; it can lead to non-repeatable reads and lost updates.

Performance Advantage

Concurrent transactions that require shared lock for get accessor methods can go ahead and access the bean, an update call is avoided if the bean state was not modified as part of the transaction.

Related Topics:

• Concurrency types
• Repeatable Read
• Optimistic Repeatable Read - set this to verify all, modified, or modified and accessed fields
• Read Only
• How to setup Concurrency Control for CMP Beans

© Pramati Technologies 2007	Runs on Pramati Server | Feedback | Legal