This week's book giveaway is in the Clojure forum.
We're giving away four copies of Clojure in Action and have Amit Rathore and Francis Avila on-line!
See this thread for details.
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Stateless session bean

 
Matt Sumner
Greenhorn
Posts: 19
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a stateless session bean that is being removed, ejbRemove called, after every method invocation.
I thought it should be putting the bean in to the object pool. Indeed JRun does this.
Have I deployed it incorrectly ?
I looked at the websphere container code, ( i.e. reverse engineered it), and it seems to call ejbRemove if the bean is not 'reentrant'. Otherwise it goes in to the pool.
I thought session beans are not 'reentrant' so does this mean something different here ?
 
Simon Song
Ranch Hand
Posts: 217
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
WebSphere has instance pool size setting for the EJB container, by default it is minimum 50, maximum 500.
It is configurable after FP4 for WAS4.0 through admin.config file.
 
Matt Sumner
Greenhorn
Posts: 19
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ok.... but what does that mean ?
Minimum of 50 what ? And maximum of 500 what ?
Ultimately I would like me stateless session bean to hang around between calls.
 
Simon Song
Ranch Hand
Posts: 217
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
instances
 
Matt Sumner
Greenhorn
Posts: 19
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So a minium of 50 instances means it should create 50 instances on start up, creating more as necessary, but never going over a limit of 500.
That's not happening... there's only ever one instance and it's removed after every call on the bean.
Is this normal behaviour ?
 
Simon Song
Ranch Hand
Posts: 217
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Check out this:
http://www7b.software.ibm.com/webapp/wsdd/wasServlet3?client=form210&SID=1035479274198&SAVEKEY=64
If you think what you see if what websphere constantly behaves, you might open a PMR against IBM on this issue.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic