Blocked entry tasks not rescheduled on transaction end

[T.Doenz]

Blocked entry tasks (read, take, test, delete, write) are not rescheduled, although they should be, under certain conditions. For example, if a take (or read, test, delete) is performed on an empty container with an explicit transaction, the task is blocked but not rescheduled when the explicit transaction ends (commit or rollback). The reason is, that when the take operation returns with DELAYABLE, no LogItem is added to the transaction log, and thus the container used in the operation is not returned by DefaultTransaction.getAccessedContainers called in SynchronizedWaitAndEventManager.processTransactionCommit/Rollback. This is the case for the CAPI-3 status DELAYABLE and LOCKED. The write operation is affected only when it returns with LOCKED because the container is locked, otherwise a LogItem is added before the actual operation (writing the entry to the container) is performed.

[T.Doenz]

Test cases showing this bug are in the class Ticket74BlockedTaskNotRescheduledOnTxEnd (module core-integration-test).

[T.Doenz]

fixed with SVN rev. 11080