Stale data when db is shared

Question

          I asked a question to a WebLogic salesrepresentative, how to avoid stale data when the db is shared, without doing ejbLoad() for each transaction.
          He told me that if two WebLogic Servers, in a cluster setup, access the same database, and have CMP entity EJB's deployed with dbIsShared=false, the containers communicate and inform eachother that an update has taken place, which id and home, which triggers an ejbLoad(), in the container that needs updating.
          I think he meant WLS6.0, but going through the docs I haven't found anything to confirm this.
          Is this possible in WLS6.0?
          

Answer 1

When you are using a WLS cluster, db-is-shared must be set to true.
          The EJB container will ensure transactional consistency by reloading the
          data on transaction boundaries.
          If you are attempting to model browsable data with entity beans, I would
          suggest that you look into read-only entity beans. These are cached
          throughout the cluster and periodically refresh themselves from the
          database. You can also look into the docs for the Read-Mostly pattern
          where readers access the cached read-only beans and transactional
          clients access a read/write bean.
          -- Rob
          hjo1620 wrote:
          >
          > I asked a question to a WebLogic salesrepresentative, how to avoid stale data when the db is shared, without doing ejbLoad() for each transaction.
          >
          > He told me that if two WebLogic Servers, in a cluster setup, access the same database, and have CMP entity EJB's deployed with dbIsShared=false, the containers communicate and inform eachother that an update has taken place, which id and home, which triggers an ejbLoad(), in the container that needs updating.
          >
          > I think he meant WLS6.0, but going through the docs I haven't found anything to confirm this.
          >
          > Is this possible in WLS6.0?