File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes EJB and other Java EE Technologies and the fly likes Instance pooling in Entity Beans Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Instance pooling in Entity Beans" Watch "Instance pooling in Entity Beans" New topic

Instance pooling in Entity Beans

Ramesh Talwar

Joined: Jun 20, 2001
Posts: 16
Hi all
As per EJB 1.1 in entity beans the instances are pooled
and can be reused.
Then as per specs I understand that if max pool size is
reached and the there certain non-locked instances in
pool and if client tries to create entity bean then
container should reused this instances and associate it
to EJBobject.
But I have observed that in Weblogic 5.1 if pool is full
and new entity bean is created,
Container passivates one of the instances, calls
unsetEntityContext, removes instance from pool
and creates new instance for entity bean class.
Is this the expected behaviour or is weblogic not
following the specs or i am going wrong

Thanks in advance
I agree. Here's the link:
subject: Instance pooling in Entity Beans
It's not a secret anymore!