Urgent!Poor performance in Entity beans

Question

we're using Weblogic 5.1, Oracle 8i.(both installed in Solaris 5.8) We
found that the performance of our entity beans is poor, the reason we
guess is because when we issue a select statement, the jdbc, at the same
time, issue a update statement, that's why the response time is slow.
(By the way,we use oracle thin driver to connect.)
I know we can set autocommit to false but our beans are cmp,so we can't
set properties in connection pool.What can we do then?Can we set any
transaction attributes in our ejb,so we can solve our problem?
Thx!
Pete

Answer 1

A few issues with the linked article:
" 1. Where ever possible, using Entity bean with CMP over Entity bean with BMP, will ensure increase in performance... Tuned CMP entity beans offer better performance than BMP entity beans."
Bull. Every time I have seen some statement like the above it has never contained any associated proof nor explaination of how a container vendor's code can interact with a DB any better than mine.
The only means by which a container vendor can generically improve the performance of DB interactivity is to not do it, namely by caching the data and monitoring modification. This is rarely used due to mitigating factors such as any case where the container does not have sole access and omniscience over the DB.
"Moving towards the CMP based approach provides database independence since it does not contain any database storage APIs within it."
Ahh yes, lets trade in EJB container independence for database independence. It's interesting that the biggest proponents of CMP (and the ones who pushed it into the spec) are the biggest container vendors. Database storage APIs??? Perhaps JDBC and "select * from USER where..." are somehow viewed as database specific.