We have also been experiencing something similar, and also haven't been confident enough to report it as a bug as we have been in heavy development of lots of components and its entirely possible there is bug in our code. One thing that we are doing though is using a central lookup table that contains a mapping from a primary key to a entity type. I wont go into the reasons for this design (and yes I know there are many criticisms!), but what it allows us to do is have a session bean do a lookup on the entity based purely on id (in our case a long). I'm curious to hear if other people who are experiencing this have similar designs? eg: +-------------+ +-------------+ +-------------------------------+ | Entity A | | Entity B | | StatelessSessionBean | +-------------+ +-------------+ +-------------------------------+ | -pk:long | | -pk:long | | +lookupEntity(pk:long):Entity | | (other | | (other | | | | properties) | | properties) | | | +-------------+ +-------------+ +-------------------------------+ We've only just started experiencing this, and I haven't had time to develop a test case for this but in light of this I will try to put the test case further up my todo list. If I can get a firm test case I will submit it. As far as I can see atm the key factor seems to be a delay in time. Get an instance of the entity in memory, then leave it for a while, then use it again - at that point it has incorrect values. There might also me something to do with changing it beforehand. Like I said I will get a test case in ASAP. System: JBoss 2.1 using CMP cheers dim > From: Richard Conway <[EMAIL PROTECTED]> > To: "'[EMAIL PROTECTED]'" > <[EMAIL PROTECTED]> > Subject: RE: [JBoss-user] Re: [JBoss-dev] Serious Bug? EntityBean out of > synch with database. > Date: Wed, 6 Jun 2001 10:50:45 +0100 > Reply-To: [EMAIL PROTECTED] > > 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. _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
