The default transaction isolation level of EJB3 beans is READ_COMMITED.
Optimistic locking mechanism of entity bean will not work with isolation level higher than READ_COMMITED. (Optimistic locking only works if non-repeatable read exists, right?)
But the default isolation level of ejb3 entity cache is REPEATABLE Read (defined in ejb3-entity-cache-service.xml).
I cannot understand the why the isolation level of ejb3 entity cache is set to such a default value? Is there any special reason? Could there be any risk if I use READ_COMMITED for ejb3 entity cache?
