0

we know that the stateless sessions beans (JEE5 context) can be pooled. I was wondering what happens when the Server's pool of stateless session beans has no more instances left and another client request comes in...

a) Is the client request put in a (blocked) waiting state OR

b) the server refuses the connection right away.. OR

c) Can we handle this situation programmatically to give a customized response based on the SLA of our specific application

Robin Bajaj
  • 2,002
  • 4
  • 29
  • 47

1 Answers1

2

It varies from vendor to vendor. WebSphere Application Server will create new instances as required, and it will remove beans when returning them to the pool if the pool has reached its maximum size. The product also can be configured to have a hard limit using the poolSize option that causes requests to block until a bean becomes available.

Brett Kail
  • 33,593
  • 2
  • 85
  • 90
  • Great... thanks for your response.. I found some similar options for my server (weblogic in this case)... just putting them here for anybody else who might have the same question http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ejb/session.html#wp1132096 – Robin Bajaj Apr 13 '11 at 17:07