Hello,
In my project we need to use read-ahead strategies. I have a situation where concurrent read access to the bean have to be allowed. Since for the read-ahead strategies to work the transaction attribute must be
Required/RequiresNew
I have set it as Required.
I have extended the Standard CMP entity bean and created a container configuration with
SimpleReadWriteEJBLock
as locking policy. For the beans I have specified the optimistic locking strategy with time-stamp column approach. The methods have a
Required
transaction attribute set.
Now when concurrent read access occurs
TrasactionRolledBackException
is happening due to read time out. I cannot use read only entity beans since such beans are not part of transaction and read ahead strategies will have a negative performance impact.
Can somebody provide some clues to fix the issue?
What I need is,
1. Concurrent read access is permitted
2. read-ahead strategies should work properly
Any Ideas?
Thanks
Arun K
