Hi Folks,
I am trying to come up with a good cache invalidation strategy for our
entity EJBs that are updated infrequently and accessed often. On a
cluster cache consistency becomes a problem so I had the following ideas
for invalidation strategy:
1.
Has anyone tried working with entity EJB's that are read-only in cluster
environment, and doing invalidation of replica entities using JMS
messages (JMS is clustered in WL 6.0, or point-to-point can be used in
earlier releases).
Any comments on performance/issues with this solution.
2.
Has anyone tried using Oracle's Java triggers, to call
refresh() on entity EJB's, maintaining consitency that way?
3.
Using JNDI (it is clustered by WL) to register and de-register active
entity beans, and at a to invalidate data just lookup all relevant
active beans in the cluster and call an invalidate() method on them
thanks in advance for your thoughts on this,
- Ilya
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
