I know this is OT, but the thread reminded me of this...
Has anyone looked at using something like "JSR-107: JCACHE - Java
Temporary Caching API" to help in keeping cached entity beans in a
cluster synchronized instead of relying solely on the database?
David Jencks wrote:
>I don't see a respo
> I don't see a response yet from the experts...so I will jump in.
Sometimes, I sleep ;)
> Don't use commit option A with clustering, and do use whatever your
> database supplies for select for update. The clustering implemention
> relies on database locking to synchronize the different copie
Hello Dennis,
For now, for entity beans, we use pessimistic locking at the database level i.e. we
use the ~"SELECT ... FOR UPDATE" features of databases to lock database rows.
Consequently, you need to run in commit option C (or B if you have a kid whose name
starts with a B... it won't make a
I don't see a response yet from the experts...so I will jump in.
Don't use commit option A with clustering, and do use whatever your
database supplies for select for update. The clustering implemention
relies on database locking to synchronize the different copies of entities.
I actually don't
