O'Reilly logo

Special Edition Using Enterprise JavaBeans™ 2.0 by Brian Keeton, Chuck Cavaness

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Isolating Access to Resources

Early in this chapter you saw that a characteristic of a transaction is that it be isolated from the effects of other transactions. Isolation isn’t as rigid a requirement as the other ACID properties so you have some leeway in how it’s enforced in your applications. To reflect this, resource managers support one or more isolation levels. An isolation level describes the extent to which access to a single resource by concurrent transactions is separated.

The need to isolate transactions is best understood when you consider the interactions that can occur between concurrent transactions when they aren’t kept apart. These interactions are called isolation conditions and they consist of dirty reads, nonrepeatable reads, ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required