I would second Filip's comment. locking tomcat in this fashion is not advised, unless you have solid experience with it. It's not as easy as one would think.
peter On Thu, 30 Sep 2004 10:36:34 -0500, Filip Hanik - Dev <[EMAIL PROTECTED]> wrote: > sounds like your system needs a little rethinking, if you have singleton access to > your DB. > That is why the DBs are transactional, so that you can use connection pooling. > > you can use JGroups, but you might run into serious performance problems, not > because of JGroups, but because of the fact that you > want to lock several tomcats in a distributed lock when accessing the DB. > > Filip > > > > > ----- Original Message ----- > From: "Igor" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, September 30, 2004 10:16 AM > Subject: Re: Synchronization in cluster > > Hello! > > Thank you for answers! I will try to use JGroups > > We have data, that is often need to be read. And it is rarely written. > It is implemented using Singleton pattern. > > Synchronization is used in several parts of web application. > It is used mostly to access database > > Thank you, > Igor > > ----- Original Message ----- > From: "LERBSCHER Jean-Pierre" <[EMAIL PROTECTED]> > To: "'Tomcat Users List'" <[EMAIL PROTECTED]> > Sent: Thursday, September 30, 2004 10:41 AM > Subject: RE : Synchronization in cluster > > Hi, > What are your needs? Why distributed singleton or distributed locking are so > important ? > Perhaps you can use Database to implement locking functionality and Jgroups > library to replicate state (or distributed singleton) across members of a > group (see www.jgroups.org). > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
