Very high CPU utilization and a hung thread were found during certain IICTs (Immediate Independent Commit Transactions). The routine that evaluates whether or not a key level lock is associated with an active transaction uses hash bins to match a transaction number with the thread that owns the transaction. In the unlikely situation that both the encompassing transaction and the IICT were assigned to the same hash bin, an infinite loop could occur. The logic has been changed to correctly handle this situation.