Hi!
"Day, Jem BGI WAC" wrote:
> Be aware that this does not only relate to the
> issue of server location (DNS Round Robin, Load
> balance etc), but also ensuring that a given
> instance of an Entity bean only exists in one
> of the servers in the cluster - which i think
> is the more difficult bit.
Nope, they don't do this. And I quote
(http://www.beasys.com/products/weblogic/server/clustering.pdf):
"The activation service can avoid concurrency conflicts here simply by
relying on underlying database locking. In a
WebLogic cluster, EJB entity beans default to this approach."
So they don't do it the difficult way but relies on the db. By doing
this you cannot do caching between tx's (unless you are doing CMP in
which case it is possible to be a little more clever with timestamping
and such).
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
