This sounds exactly like the problem we are experiencing intermittently. The web tier asks for the details for a particular company, and is returned the data for a different company. Once the problem occurs it seems to latch for a period of time - sometimes, if left the situation resolves itself, other times a JBoss restart has been required. Each company is identified by an id which forms part of the beans primary key. When the problem occurs there will be a particular company whose details are returned incorrectly, whilst accesses to other companies is delivered correctly. Returning to the problematic company again returns the wrong details. In all cases the data in the database is fine and the web tier is asking for the right primary key. It's as if Jboss is sometimes confused and returns what it thinks is the right bean for the find() request, i.e. JBoss' EJB cache has lost sync of which EJB is for which primary key. The problem seems more likely to occur when the system is supporting numerous concurrent users. We are using JBoss 2.0 FINAL with BMP. Solaris 2.6 [Java HotSpot(TM) Client VM (build 1.3.0, mixed mode)] I had assumed that this was a bug in our code - something I was planning on looking at immediately. However, if other people have the same problem then maybe the fault lies elsewhere. Richard. -----Original Message----- From: danch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 06, 2001 4:01 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] Re: [JBoss-dev] Serious Bug? EntityBean out of synch with database. This sounds _very_ like the problem Andre Vermeulen has reported. Just to confirm, you are using CMP, correct? Also, can you verify that ejbFindByPrimaryKey _does_ work? Bill Burke wrote: > All, Please help, > > > > We experienced some very strange behaviour. A queried EntityBean via a > findBy column method had the wrong data within it. It actually had the > data from a different EntityBean. Querying the database directly showed > that the database had the correct data within it. Even stranger, this > problem went away after a few minutes. > > > > My guess is that the EntityBean instance somehow got populated with bad > data and after a few minutes, got passivated( or whatever) out of the > bean cache. What I don't get is that I'm using commit option 'B' for > entity beans. Shouldn't the EntityBean be re-loaded from the database > at the start of any transaction? > > > > Machine stats: > > > > dual CPU 800Mgz Intel running RedHat 6.2 > > JBoss 2.2.1 > > Sun's jdk1.3.0.0.2 > > commit option 'B' > > > > I know this is a JBoss-User question/problem, but I view this as a > really serious problem that needs close scrutiny. > > > > Thanks, > > > > Bill > > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
