enity bean performance && commit options B/C

Hi guys!

I really do need your experience.

If your app server isn't the only system accessing and possibly mutating certain tables in the database you have to choose commit options B/C.

Does anybody know how the different app servers implement the task of ensuring the correct state of entity beans?

Are they really reloading the state from the database every time I access a getter?

Isn't this a really huge performance hit and is anyone able to provide something more concrete than 'huge'?

Do you know of some 'special tricks' IBM WAS does with DB2 and Oracle AS does with Oracle DB?

Thank you very much for your help!

Best regards,
Juergen

"JuergenP JuergenP",

We're pleased to have you here with us in the EJB forum, but there are a few rules that need to be followed, and one is that proper names are required. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it.

In particular, your display name must be a first and a last name separated by a space character, and must not be obviously fictitious.

Thanks,
Jeanne
Forum Bartender
[ February 09, 2005: Message edited by: Jeanne Boyarsky ]

Sorry about my login name.

Currently it 's 3:46 am my time and I'll correct my login name in the morning.

I didn't think about login name policies but just wanted to ask some serious questions.

My name is Juergen Petri from Osnabrueck, Germany.

Have a good nights sleep

Juergen

Hi, you�ll find information on ejbLoad and ejbStore behavior and also how to control it at:

http://e-docs.bea.com/wls/docs81/ejb/entity.html#1107234

regards.

The above link is for weblogic 8.1 thought.

Originally posted by JuergenP JuergenP:
Sorry about my login name.

No problem! Thanks for updating the name!

And in response to your question: it depends on your transaction settings. Marcos' link explains it well. This behavior conforms to standards and isn't app server specific.