In Progress 9.1E04, OpenEdge 10.0B03 and later, the TXE algorithm was changed in an effort to ensure that TXE Commit Locks will not be starved. For further information refer to Article P121754,
How to change the Commit Lock Skip Limit for the TXE in promon? Upgrade to OpenEdge 10.1B or later where a
database startup parameter -TXESkipLimit to set the TXE commit lock skip limit was introduced.
- Default value is 10000, to set the maximum SHARE/UPDATE locks that can skip the queued COMMIT locks,
- The commit lock skip limit ranges is: (0 to 100000)
- The value needs to be changed in a large scale. For example, by changing it from 10000 to 10001
should not make any difference if it is indeed this TXE latch contention causing the performant issue - Setting it to 0 (zero) will restore to the old TXE locking algorithm to favour COMMIT locks.