Exclusive lock on record is held beyond the end of the transaction scope

Exclusive lock on record is held beyond the end of the transaction scope
Using FOR FIRST <buffer> EXCLUSIVE-LOCK
Referring to buffer after the FOR FIRST block

Example code:

FOR FIRST Customer EXCLUSIVE-LOCK TRANSACTION:
    LEAVE.
END.

FIND FIRST _Lock WHERE _Lock-Recid = INTEGER(RECID(Customer)) NO-ERROR.

DISPLAY _Lock-Flags Transaction.

In this code, the RECID() function refers to the buffer, thus pushing the record scope beyond the transaction scope.
The DISPLAY statement above will display and 'X' for the _Lock-Flags which indicates that the record still has an exclusive lock.
Note that in many cases, one would expect the lock to be dropped entirely after the FOR FIRST block.
This will not happen automatically, but can be forced by a FIND CURRENT <buffer> NO-LOCK immediately after the block.

The exact cause is not known at this time.

Upgrade to OpenEdge 10.0B or later.
 In the later releases the record lock is properly downgraded to share-lock.

References to written documentation:

Progress Articles:
How Transactions work in Progress