Excuse my ignorance, but shouldn't the container be able to handle all of the findByPrimaryKey calls without passing it onto the entity bean's findByPrimaryKey -- if the entity beans are in memory. (Same home and same primary key = same entity bean.) If it can't find them in memory, then, and only then, it should pass on the call to a free entity bean in the pool. I have been running a test in WebLogic of an entity bean that I create with a primary key, and then I do a findByPrimaryKey on it immediately after that. It calls my routine. (!) Going out to persistent storage may be an expensive operation (especially if the data is not in an RDBMS or ODBMS) so it would be good if having the beans in memory meant that the container would use them. Is this a transaction-related problem in my deployment that I have screwed up? Thanks, - Mark _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
