A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
Win a copy of
Spring in Action
this week in the
EJB and other Java EE Technologies
how do we specify the max stateful beans in the pool
Joined: Mar 13, 2006
Dec 05, 2006 04:44:00
i am trying the simulate the scenario where ejbActivate() and ejbPassivate() would be triggered.i am using weblogic8.1.
my weblogic-ejb-jar.xml goes like this.
And i am creating the remote objects thrice.As per my descriptor(the max bean in the pool is 2),passivation must happen.
But that is not happening.
when you really want something, all the universe always conspires in your favour.<br /> <br />SCJP1.5-77%<br />SCWCD-89%
Joined: Feb 05, 2001
Dec 05, 2006 06:23:00
Actually stateful Session Beans are not pooled, the exist only for one client. So when the client first looks up a Stateful bean, one gets created, not taken from any pool, and when the client is finished the bean gets destroyed.
Perfect World Programming, LLC
Two Laptop Bag
How to Ask Questions the Smart Way FAQ
Joined: Feb 18, 2005
Dec 07, 2006 03:19:00
2.1 spec SFSB can be passivated after timeout. Try to play with container settings.
SCJP 1.4 (100%) Done.<br />SCJD (URLyBird 1.2.3 Started)
It is sorta covered in the
JavaRanch Style Guide
subject: how do we specify the max stateful beans in the pool
EJB Passivate and EJB Remove for stateful Bean are not called by weblogic
Why ejbPassivate and ejbRemove are not called by weblogic container?
Seting instance pool limit for stateful session bean
How to simulate stateful session bean program on weblogic server?
Restricting number of stateful session beans
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2014