The Enterprise Java Bean Pool property editor enables you to specify the bean pool properties. You open the Enterprise Java Bean Pool property editor by selecting the Bean Pool property and its ellipsis (...) button from the Sun ONE AS pane of an enterprise bean's property sheet.
This field specifies the initial and minimum number of bean instances that should be maintained in the pool.
This field specifies the maximum number of bean instances that can be created to satisfy client requests. The possible values are from 0 to MAX_INTEGER.
This field specifies the number of bean instances to be created if a request arrives when the pool is completely busy (subject to the limit specified in the Max Pool Size field). The possible values are from 0 to MAX_INTEGER.
This field specifies the maximum time, in seconds, that a bean instance is allowed to remain idle in the pool. When this timeout expires, the bean instance in a pool becomes a candidate for passivation or deletion.
![]() |
For a stateless session bean, the bean can be removed (garbage collected) when the timeout expires. |
this field specifies the maximum time, in milliseconds, the caller waiting to get a bean from the free pool will wait before getting a connection timeout. If the value specified is 0, wait time is infinite. If overflow is not allowed, some currently cached instances may be passivated to make room for the new instance. When all else fails, an exception is thrown.
See also | |
BMP Bean Property Sheet: Sun ONE AS Tab CMP Bean Property Sheet: Sun ONE AS Tab Session Bean Property Sheet: Sun ONE AS Tab Message-Driven Bean Property Sheet: Sun ONE AS Tab |