RE: Simple question re caching/pooling of BMP Entity Beans
You can avoid the call. Using a combination of isModified, validity_timeout and transaction_isolation ... just play around with it for a bit. See the online Orion FAQ: http://www.orionserver.com/faq/ I am using CMP Entity beans and call many methods on it that do not modify the state of the bean. How can I help Orion figure out that I am not changing the state and that it does not need to talk to the database? Implement the method public boolean isModified() in your bean to return a boolean flag that you set each time you modify your bean and clear in ejbStore(). If isModified() returns false, Orion knows that it doesn't need to talk to the database Regards, Manuel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Geoff Soutter Sent: Friday, January 11, 2002 7:13 AM To: Orion-Interest Subject: RE: Simple question re caching/pooling of BMP Entity Beans Hmm. Seems I am really getting myself confused. :-). I think I've got it now... I'm mistaking the db call in ejbFindByPrimaryKey with the db call in ejbLoad. Doh. So, the first time I call findByPrimaryKey, Orion calls ejbFindByPrimaryKey which goes to the database basically only to confirm the row hasn't been deleted. Then Orion calls ejbLoad which goes the the database again to load in the actual contents of the row. So, the row in question is accessed twice. Then, the second time, Orion still calls findByPrimaryKey, but avoids the ejbLoad. The thing is here, exclusive-write-access is set to true (by default), so why is Orion bothering to call findByPrimaryKey? Can't it just keep an internal primary key - ejb map and return the ejb instance directly? After all, if exclusive-write-access is on, the row can only be deleted by Orion itself... Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Geoff Soutter Sent: Friday, 11 January, 2002 9:09 AM To: Orion-Interest Subject: RE: Simple question re caching/pooling of BMP Entity Beans Hi Sergey, Thanks for the reply. I didn't explain it very clearly did I? What I meant was: However, it appears that it goes to the database (i.e. calls _ejbLoad_ in the Entity Bean's implementation) for every call to findByPrimaryKey, regardless of whether it has previously read the instance with the specified key before. Have you been able to get pooling of BMP entity beans working? Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Sergey G. Aslanov Sent: Thursday, 10 January, 2002 6:29 PM To: Orion-Interest Subject: Re: Simple question re caching/pooling of BMP Entity Beans Hi Geoff Loading of beans have these stages: 1. calling ejbFindBy... to get the primKeys of the entities; 2. checking if entities with such keys are already pooled; 3. for every key checking: if not pooled - call ejbLoad, else - get instance from pool; As you see, ejbFindBy... are called always independently of entity is pooled or not. Thursday, January 10, 2002, 2:01:37 AM, you wrote: GS Hi there, GS I'm teaching myself how to use Orion and I've got a simple question GS about caching/pooling of BMP Entity Bean instances. GS I've created a simple app which lets me read a BMP Entity Bean GS through a Session Bean. I would expect that when I call GS findByPrimaryKey on my Entity Bean's home interface, Orion caches GS the instance it creates so that next time I call findByPrimaryKey GS for the same key, it just returns the instance it already has rather GS than creating a new one. However, it appears that it goes to the GS database (i.e. calls ejbFindByPrimaryKey in the Entity Bean's GS implementation) for every call to findByPrimaryKey, regardless of GS whether it has previously read the instance with the specified key GS before. GS I checked the list archive and it appears that someone has reported GS a similar problem a while back but there were no replies GS (http://www.mail-archive.com/orion-interest@orionserver.com/ms g17359 GS .htm GS l). GS I also checked the documentation and for orion-ejb-jar.xml it states GS that exclusive-write-access is true by default, and since I am not GS setting it I presume it's defaulting to true which should allow GS Orion to cache the entity beans. GS So, can anyone shed any light on how whether/how I can get Orion to GS cache BMP entity beans? GS Cheers GS Geoff -- Sergey G. Aslanov, CBOSS Group, Web-technologies department mailto:[EMAIL PROTECTED] tel: +7 095 7555655
Re: Simple question re caching/pooling of BMP Entity Beans
My opinion would add; if not pooled OR not exclusive owner of data then ejbLoad exclusive owner is an orion-ejb-jar.xml propert. The default is, exclusively owns the data. curt Sergey G. Aslanov wrote: Hi Geoff Loading of beans have these stages: 1. calling ejbFindBy... to get the primKeys of the entities; 2. checking if entities with such keys are already pooled; 3. for every key checking: if not pooled - call ejbLoad, else - get instance from pool; As you see, ejbFindBy... are called always independently of entity is pooled or not. Thursday, January 10, 2002, 2:01:37 AM, you wrote: GS Hi there, GS I'm teaching myself how to use Orion and I've got a simple question GS about caching/pooling of BMP Entity Bean instances. GS I've created a simple app which lets me read a BMP Entity Bean through a GS Session Bean. I would expect that when I call findByPrimaryKey on my GS Entity Bean's home interface, Orion caches the instance it creates so GS that next time I call findByPrimaryKey for the same key, it just returns GS the instance it already has rather than creating a new one. However, it GS appears that it goes to the database (i.e. calls ejbFindByPrimaryKey in GS the Entity Bean's implementation) for every call to findByPrimaryKey, GS regardless of whether it has previously read the instance with the GS specified key before. GS I checked the list archive and it appears that someone has reported a GS similar problem a while back but there were no replies GS (http://www.mail-archive.com/orion-interest@orionserver.com/msg17359.htm GS l). GS I also checked the documentation and for orion-ejb-jar.xml it states GS that exclusive-write-access is true by default, and since I am not GS setting it I presume it's defaulting to true which should allow Orion to GS cache the entity beans. GS So, can anyone shed any light on how whether/how I can get Orion to GS cache BMP entity beans? GS Cheers GS Geoff -- Sergey G. Aslanov, CBOSS Group, Web-technologies department mailto:[EMAIL PROTECTED] tel: +7 095 7555655 -- Curt Smith [EMAIL PROTECTED] (w) 404-463-0973 (h) 404-294-6686
RE: Simple question re caching/pooling of BMP Entity Beans
Hi Sergey, Thanks for the reply. I didn't explain it very clearly did I? What I meant was: However, it appears that it goes to the database (i.e. calls _ejbLoad_ in the Entity Bean's implementation) for every call to findByPrimaryKey, regardless of whether it has previously read the instance with the specified key before. Have you been able to get pooling of BMP entity beans working? Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Sergey G. Aslanov Sent: Thursday, 10 January, 2002 6:29 PM To: Orion-Interest Subject: Re: Simple question re caching/pooling of BMP Entity Beans Hi Geoff Loading of beans have these stages: 1. calling ejbFindBy... to get the primKeys of the entities; 2. checking if entities with such keys are already pooled; 3. for every key checking: if not pooled - call ejbLoad, else - get instance from pool; As you see, ejbFindBy... are called always independently of entity is pooled or not. Thursday, January 10, 2002, 2:01:37 AM, you wrote: GS Hi there, GS I'm teaching myself how to use Orion and I've got a simple question GS about caching/pooling of BMP Entity Bean instances. GS I've created a simple app which lets me read a BMP Entity Bean GS through a Session Bean. I would expect that when I call GS findByPrimaryKey on my Entity Bean's home interface, Orion caches GS the instance it creates so that next time I call findByPrimaryKey GS for the same key, it just returns the instance it already has rather GS than creating a new one. However, it appears that it goes to the GS database (i.e. calls ejbFindByPrimaryKey in the Entity Bean's GS implementation) for every call to findByPrimaryKey, regardless of GS whether it has previously read the instance with the specified key GS before. GS I checked the list archive and it appears that someone has reported GS a similar problem a while back but there were no replies GS (http://www.mail-archive.com/orion-interest@orionserver.com/ms g17359 GS .htm GS l). GS I also checked the documentation and for orion-ejb-jar.xml it states GS that exclusive-write-access is true by default, and since I am not GS setting it I presume it's defaulting to true which should allow GS Orion to cache the entity beans. GS So, can anyone shed any light on how whether/how I can get Orion to GS cache BMP entity beans? GS Cheers GS Geoff -- Sergey G. Aslanov, CBOSS Group, Web-technologies department mailto:[EMAIL PROTECTED] tel: +7 095 7555655
Re: Simple question re caching/pooling of BMP Entity Beans
pooling definitely does work for BMP.
couple of things i found that you might want to check off.
1. implement an isModified method
public boolean isModified() {
return false;
}
which orion will check to determine if ejbLoad needs to be called. we're
using the value object pattern to the above works for us. you may want to
make it more complicated depending on your requirements.
2.. return a Collection from your finder methods. returning an Enumeration
seems to cause orion to not pool.
3. if you have defined your own primary key instead of using, say, Integer,
it seems you need to implement equals() and hashCode().
if you can't get it working maybe post the code from one of your bean
classes.
good luck,
greg.
- Original Message -
From: Geoff Soutter [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Friday, January 11, 2002 8:08 AM
Subject: RE: Simple question re caching/pooling of BMP Entity Beans
Hi Sergey,
Thanks for the reply. I didn't explain it very clearly did I? What I
meant was:
However, it appears that it goes to the database (i.e. calls _ejbLoad_
in the Entity Bean's implementation) for every call to findByPrimaryKey,
regardless of whether it has previously read the instance with the
specified key before.
Have you been able to get pooling of BMP entity beans working?
Geoff
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of
Sergey G. Aslanov
Sent: Thursday, 10 January, 2002 6:29 PM
To: Orion-Interest
Subject: Re: Simple question re caching/pooling of BMP Entity Beans
Hi Geoff
Loading of beans have these stages:
1. calling ejbFindBy... to get the primKeys of the entities;
2. checking if entities with such keys are already pooled;
3. for every key checking: if not pooled - call ejbLoad, else
- get instance from pool;
As you see, ejbFindBy... are called always independently of
entity is pooled or not.
Thursday, January 10, 2002, 2:01:37 AM, you wrote:
GS Hi there,
GS I'm teaching myself how to use Orion and I've got a
simple question
GS about caching/pooling of BMP Entity Bean instances.
GS I've created a simple app which lets me read a BMP Entity Bean
GS through a Session Bean. I would expect that when I call
GS findByPrimaryKey on my Entity Bean's home interface, Orion caches
GS the instance it creates so that next time I call findByPrimaryKey
GS for the same key, it just returns the instance it already
has rather
GS than creating a new one. However, it appears that it goes to the
GS database (i.e. calls ejbFindByPrimaryKey in the Entity Bean's
GS implementation) for every call to findByPrimaryKey, regardless of
GS whether it has previously read the instance with the
specified key
GS before.
GS I checked the list archive and it appears that someone
has reported
GS a similar problem a while back but there were no replies
GS
(http://www.mail-archive.com/orion-interest@orionserver.com/ms
g17359
GS .htm
GS l).
GS I also checked the documentation and for orion-ejb-jar.xml it states
GS that exclusive-write-access is true by default, and since I am not
GS setting it I presume it's defaulting to true which should allow
GS Orion to cache the entity beans.
GS So, can anyone shed any light on how whether/how I can get Orion to
GS cache BMP entity beans?
GS Cheers
GS Geoff
--
Sergey G. Aslanov,
CBOSS Group,
Web-technologies department
mailto:[EMAIL PROTECTED]
tel: +7 095 7555655
Re: Simple question re caching/pooling of BMP Entity Beans
Hi Guys. Having just finished solving some headaches on this topic, my comment is, what are you guys doing differently from me? One of our ex-guys was nice enough to write a mess of code to update data that an entity EJB used/stored, but rather than updating the EJB, the database was updated directly. Since the EJB (BMP) was being cached, not loaded, and had a verrry long time out (intentional), this was producing some really nasty bugs. To get the data to load, we had to stop and restart the server. And I can very that findByPrimaryKey was most definately getting called. One thing I did notice, from very early in the project. Left to its defaults, the timeout on an Entity EJB in Orion is very short. It may be unloaded between consecutive calls. For example, the following block of code did result in three calls of ejbLoad on the entity EJB until we reset the time-out. UserHome userHome = getUserHome(); //Returns home interface to UserEntityEJB User user = userHome.findByPrimayKey(username); //Returns Remote Interface to Entity EJB user.login(password); UserData data = user.getData(); I forget where off hand to set the EJB Time-out, but I think it was either the ejb-jar.xml, or the orion-ejb-jar.xml file. If you need, I can look it up and let you know. -Steve Geoff Soutter wrote: Hi Sergey, Thanks for the reply. I didn't explain it very clearly did I? What I meant was: However, it appears that it goes to the database (i.e. calls _ejbLoad_ in the Entity Bean's implementation) for every call to findByPrimaryKey, regardless of whether it has previously read the instance with the specified key before. Have you been able to get pooling of BMP entity beans working? Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Sergey G. Aslanov Sent: Thursday, 10 January, 2002 6:29 PM To: Orion-Interest Subject: Re: Simple question re caching/pooling of BMP Entity Beans Hi Geoff Loading of beans have these stages: 1. calling ejbFindBy... to get the primKeys of the entities; 2. checking if entities with such keys are already pooled; 3. for every key checking: if not pooled - call ejbLoad, else - get instance from pool; As you see, ejbFindBy... are called always independently of entity is pooled or not. Thursday, January 10, 2002, 2:01:37 AM, you wrote: GS Hi there, GS I'm teaching myself how to use Orion and I've got a simple question GS about caching/pooling of BMP Entity Bean instances. GS I've created a simple app which lets me read a BMP Entity Bean GS through a Session Bean. I would expect that when I call GS findByPrimaryKey on my Entity Bean's home interface, Orion caches GS the instance it creates so that next time I call findByPrimaryKey GS for the same key, it just returns the instance it already has rather GS than creating a new one. However, it appears that it goes to the GS database (i.e. calls ejbFindByPrimaryKey in the Entity Bean's GS implementation) for every call to findByPrimaryKey, regardless of GS whether it has previously read the instance with the specified key GS before. GS I checked the list archive and it appears that someone has reported GS a similar problem a while back but there were no replies GS (http://www.mail-archive.com/orion-interest@orionserver.com/ms g17359 GS .htm GS l). GS I also checked the documentation and for orion-ejb-jar.xml it states GS that exclusive-write-access is true by default, and since I am not GS setting it I presume it's defaulting to true which should allow GS Orion to cache the entity beans. GS So, can anyone shed any light on how whether/how I can get Orion to GS cache BMP entity beans? GS Cheers GS Geoff -- Sergey G. Aslanov, CBOSS Group, Web-technologies department mailto:[EMAIL PROTECTED] tel: +7 095 7555655 -- Stephen Davidson Java Consultant Delphi Consultants, LLC http://www.delphis.com Phone: 214-696-6224 x208
RE: Simple question re caching/pooling of BMP Entity Beans
Hmm. Seems I am really getting myself confused. :-). I think I've got it now... I'm mistaking the db call in ejbFindByPrimaryKey with the db call in ejbLoad. Doh. So, the first time I call findByPrimaryKey, Orion calls ejbFindByPrimaryKey which goes to the database basically only to confirm the row hasn't been deleted. Then Orion calls ejbLoad which goes the the database again to load in the actual contents of the row. So, the row in question is accessed twice. Then, the second time, Orion still calls findByPrimaryKey, but avoids the ejbLoad. The thing is here, exclusive-write-access is set to true (by default), so why is Orion bothering to call findByPrimaryKey? Can't it just keep an internal primary key - ejb map and return the ejb instance directly? After all, if exclusive-write-access is on, the row can only be deleted by Orion itself... Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Geoff Soutter Sent: Friday, 11 January, 2002 9:09 AM To: Orion-Interest Subject: RE: Simple question re caching/pooling of BMP Entity Beans Hi Sergey, Thanks for the reply. I didn't explain it very clearly did I? What I meant was: However, it appears that it goes to the database (i.e. calls _ejbLoad_ in the Entity Bean's implementation) for every call to findByPrimaryKey, regardless of whether it has previously read the instance with the specified key before. Have you been able to get pooling of BMP entity beans working? Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Sergey G. Aslanov Sent: Thursday, 10 January, 2002 6:29 PM To: Orion-Interest Subject: Re: Simple question re caching/pooling of BMP Entity Beans Hi Geoff Loading of beans have these stages: 1. calling ejbFindBy... to get the primKeys of the entities; 2. checking if entities with such keys are already pooled; 3. for every key checking: if not pooled - call ejbLoad, else - get instance from pool; As you see, ejbFindBy... are called always independently of entity is pooled or not. Thursday, January 10, 2002, 2:01:37 AM, you wrote: GS Hi there, GS I'm teaching myself how to use Orion and I've got a simple question GS about caching/pooling of BMP Entity Bean instances. GS I've created a simple app which lets me read a BMP Entity Bean GS through a Session Bean. I would expect that when I call GS findByPrimaryKey on my Entity Bean's home interface, Orion caches GS the instance it creates so that next time I call findByPrimaryKey GS for the same key, it just returns the instance it already has rather GS than creating a new one. However, it appears that it goes to the GS database (i.e. calls ejbFindByPrimaryKey in the Entity Bean's GS implementation) for every call to findByPrimaryKey, regardless of GS whether it has previously read the instance with the specified key GS before. GS I checked the list archive and it appears that someone has reported GS a similar problem a while back but there were no replies GS (http://www.mail-archive.com/orion-interest@orionserver.com/ms g17359 GS .htm GS l). GS I also checked the documentation and for orion-ejb-jar.xml it states GS that exclusive-write-access is true by default, and since I am not GS setting it I presume it's defaulting to true which should allow GS Orion to cache the entity beans. GS So, can anyone shed any light on how whether/how I can get Orion to GS cache BMP entity beans? GS Cheers GS Geoff -- Sergey G. Aslanov, CBOSS Group, Web-technologies department mailto:[EMAIL PROTECTED] tel: +7 095 7555655
