-
1. Re: Entity Bean Instance pooling
amol Oct 10, 2003 4:04 AM (in response to amol)No guru to answer this ??
-
2. Re: Entity Bean Instance pooling
adrian.brock Oct 10, 2003 5:27 AM (in response to amol)The instances are cached (commit option B) by default.
Most likely you are stopping and starting transactions on
every operation?
JBoss will keep the bean instances but not the data
under option B.
Regards,
Adrian -
3. Re: Entity Bean Instance pooling
amol Oct 10, 2003 6:00 AM (in response to amol)Sir,
can you please put more light on it (commit option A and B) , how they will help in instance pooling. -
4. Re: Entity Bean Instance pooling
adrian.brock Oct 10, 2003 6:07 AM (in response to amol)Read the spec.
Instance pooling/caching is NOT your problem.
Transactions and/or read-ahead configuration are your problem.
Enable DEBUG for org.jboss.ejb.plugins in conf/log4j.xml
the look at log/server.log
I can pretty much guarantee you are seeing continual loading
due to some variation of the N+1 problem
Regards,
Adrian -
5. Re: Entity Bean Instance pooling
amol Oct 10, 2003 8:27 AM (in response to amol)Sir ,
I observed one more thing :
after ejbpassivate , container always calls unsetEntityContext .
This means that container destroyes the instance instead of putting it on pool.
is there any way , by which I can get current number of instances in a pool.
regards,