Hi, I have an issue concerning transactions, hopefully someone has experienced this as well.
PU1 creates a transaction, `changes()` a nested property (`List`) of ObjectA with the Id of ObjectB, writes ObjectB, commits transaction.
PU2 has a listener for ObjectB, is notified of the write, and then performs a `readMultiple()` for matching ObjectA(s), using a `SQLQuery` which iterates over the nested `List`. But sometimes the `readMultiple()` returns no matching results.
The `readMultiple()` uses a `READ_COMMITTED` flag. We are using the sync2backup-replication topology. The objects could be in different partitions. This transactional work is all completed in one thread on the PU1 side. The Gigaspaces proxy object has been configured with a distributed transaction manager.
Should we not be able to assume that when notified of an action that took place when a transaction was committed that the other actions have also been committed?
Thanks,
John.
↧