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 know of any other way to get consistency, but would be interested in finding out if there are other ways. david jencks On 2002.04.29 17:14:51 -0400 Dennis Muhlestein wrote: > Let's say I cluster two jboss servers and I have an Entity Bean with > commit option A. > > Are the attributes of the Entity Bean clustered? ie: user on server 1 > calls a set Method, then user on server 2 calls the get method for that > attribute. Can I expect the attribute to be current on server 2? > > If the data wasn't clustered I would say no because server 2 would think > it has exclusive access to the data (commit option A) so it wouldn't > load it. I want to know if the clustering broadcasts the attribute > changes?? > > Thanks > Dennis > > > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
