Prolonged transaction times, enforced by DirtyDO="Omit" option introduced in DODS v5.1, brought in another DB feature into our focus - database locks, and their result deadlocks.
In attempt to reduce deadlocks happening, application should honor order in tables modifications. This DBTransaction type should help coping with the task.
Using alredy described configuration feature, you specify
DatabaseManager.DB.<LogicalDatabaseName>.TransactionFactory=org.enhydra.dods.dbtransaction.ExtendedTxFactory
and you're set to go.
This type has mandatory TransactionCache, and different collection algorithm to standard implementation.