I have a java spring / hibernate based application running in test and prod environments. The application behavior is different in test and prod environments with respect transactions.
I am just using @Transactional at class level for my DB operations.
In test env the select operation is able to read uncommitted (dirty) transaction data but in prod it is not. Both test and prod DB are same except in prod we have two databases with data replication.
My question is there any specific transaction related configuration done in prod because of data replication? Or the data replication mandates a specific transaction level?
I have no details and no control over this DB configurations. Let me know what could be the possible cause of this transactional behavior.