-
1. Re: Entity bean caching
triathlon98 Aug 16, 2004 6:05 AM (in response to neva)Which commit option are you using?
I think you can only use option C.
Joachim -
2. Re: Entity bean caching
neva Aug 16, 2004 6:10 AM (in response to neva)well, I had to use Option C after failing to come up with a solution but this really weakened the advantage that caching offered to my application.
This table (represented by the 2 beans) has many records thus making caching imperative!
I need to get it back to Commit Option A :( -
3. Re: Entity bean caching
triathlon98 Aug 16, 2004 7:29 AM (in response to neva)In that case, I think you better make sure all the entity beans are in one jar.
Joachim -
4. Re: Entity bean caching
neva Aug 16, 2004 8:03 AM (in response to neva)well actually, I can't because I have to follow a specific design that makes all modules independent of each other and at the same time if used together, avoid inconsistency..
what if I use jboss cache invalidation, would that do the trick? or do they still have to be in the same jar for it to work? -
5. Re: Entity bean caching
triathlon98 Aug 16, 2004 8:29 AM (in response to neva)I am afraid this could result in race conditions. Would require serious load testing.
However, just making sure your transactions are not too small combined with commit option C would seem better/safer to me.
Joachim -
6. Re: Entity bean caching
aloubyansky Aug 17, 2004 5:15 AM (in response to neva)You can use cache invalidation. Make sure the DB's isolation level is READ_COMMITTED.