artembilan/spring-integration — comment on commit d5af04c225bf33c782e90ae2570c5fcab9aa7b78
File:  line 0
By dsyer:

If we add "FOR UPDATE" to the SQL we have to make it optional because (as you found) it isn't supported on some platforms. I think some versions of Derby do support it, but there are other problems with locks in the drivers.

If you only use Oracle you can just add PROPAGATION_SERIALIZABLE to the transaction in your message flows and I think you will get the same behaviour. I tested it and it seemed to work just fine (with a much reduced level of throughput, but that is inevitable with global locks). Do you agree?