It depends on your concurrency control scheme. You could set the JDBC drivers isolation level to force row level locking, or you could design an optimistic concurrency control scheme using counters, timestamps or before/after value checking. There is actually quite a bit of information on this topic in this lists archives. -Chris. > -----Original Message----- > From: David Gasul [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, October 28, 1999 10:12 AM > To: [EMAIL PROTECTED] > Subject: Q: Multiple EJB servers with one DB > > EJBers, > > Assume there's one (huge) DB to which we want to provide access through > EJB. > > Assume that there're multiple EJB servers that should provide access to > this DB. > > Assume that a row in the DB is represented by an entity bean. > > Now, if an entity bean has been instantiated at BOTH servers, and then > updated from one server, how is the second bean (at the 2nd server) > updated? (This is even more problematic if caching is used) > > Thx, > -- > David Gasul phone: > +972-3-5388634 > > Telegate Ltd. office: +972-3-5384600 > > 7 Haplada St., 60218 Or-Yehuda fax: +972-3-5335877 > > Israel <http://www.telegate.co.il> > > =========================================================================== 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".
