The isolation level is "READ COMMITED". > From: "Sacha Labourey" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: RE: [JBoss-user] Locking and Readonly Beans > Date: Sat, 23 Nov 2002 11:06:11 +0100 > Reply-To: [EMAIL PROTECTED] > > > Which isloation level do you use in your DB? > > > -----Message d'origine----- > > De : [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]De la part de Jon Swinth > > Envoyé : vendredi, 22 novembre 2002 18:56 > > À : [EMAIL PROTECTED] > > Objet : [JBoss-user] Locking and Readonly Beans > > > > > > > > We have been having some periodic issues with deadlock using > > JBoss 3.0.3 and > > CMP beans. In looking at the conflicts, we found that much of > > the access to > > the beans was just to read so we created readonly versions of the > > beans for > > those functions. This was done by making duplicate entries in > > the XML files > > with SomeBeanRO name and specifying the bean as readonly. The same class > > files are used for the standard and readonly versions so there > > isn't too much > > added maintenance. Now that we have done this we are seeing > > deadlocks within > > the readonly bean access. No relationships are used so there > > isn't an issue > > there. First of all, wouldn't readonly beans not need an > > exclusive lock and > > therefore wouldn't be able to deadlock? Is it possible the locking is by > > class rather than bean definition so this could be caused by the > > regular bean > > being locked? > > > > > > Between this and the fact that PostgreSQL takes a write lock > > instead of a read > > lock on foreign key tables, we are having some serious collisions > > sometimes.
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
