Sun GlassFish Enterprise Server 2.1 High Availability Administration Guide

Lock Information

Lock information is as follows:

One single transaction cannot use more than 25% of the available locks on a node. Therefore, transactions performing operations in large scale should be aware of this limitation. It is best to perform such transactions in batches, where each batch must be treated as a separate transaction, that is, each batch commits. This is needed because read operations running with repeatable read isolation level, and delete, insert, and update operations use locks that are released only after the transaction terminates.

To change the NumberOfLocks, see Clearing and Archiving History Files.

Example 3–18 Example lock information

For example:

NodeNO Avail Free Waits
0 50000 20000 101 50000 20000 0