Bug 45744

GemStone/S 64 Bit

3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1, 3.0.1, 3.0, 2.4.8, 2.4.7, 2.4.6, 2.4.5.1, 2.4.5, 2.4.4.8, 2.4.4.7, 2.4.4.4, 2.4.x, 2.3.1.6, 2.3.x, 2.2.5.4, 2.2.x, 2.x, 1.x

3.3

Inconsistent lock status after failed commit on temporary locked object

If you perform the following sequence:
   create a temporary object
   lock this temporary object using methods such as System writeLock:, etc.
   attempt a commit, but encounter a commit failure.
   abort the session

Then the lock on the temporary object remains, but is in a invalid state. The lock can't be removed, and methods to access lock status such as sessionLocks are inconsistent.

Workaround

Removing the lock before aborting avoids problems.  Using System removeLocksForSession allows you to clear the state.


Last updated: 10/22/15