Steve Ebersole Thanks for the update. Could you add the `SharedSessionContractImplementor` parameter to those methods as well?

IIUC the DirectAccessRegion.putIntoCache can be called before the transaction is committed, hence if I insert data into a non-transactional cache immediately I could expose uncommitted data (as the query can include DB-persisted-but-not-committed entities). That's why I am rather adding a synchronization to the TransactionCoordinator (or using CacheTransactionSynchronization in the close future).