TCPIP Server (Inbound) Adapter - MDB Pool Settings (Configuring Java CAPS Environment Components for Communications Adapters)

Configuring Java CAPS Environment Components for Communications Adapters

TCPIP Server (Inbound) Adapter - MDB Pool Settings

Specific to the MDB bean pool of Sun Java^TM System Application Server and Sun Enterprise Service Bus only. The parameter settings in this section are applied to sun-ejb-jar.xml.

The TCPIPServer (Inbound) Adapter - MDB Pool Settings properties contain the top-level parameters displayed in the following table.

Table 4 TCPIPServer (Inbound) Adapter - MDB Pool Settings Properties


Name	Description	Required Value
Steady Pool Size	Specifies the minimum number of MDB beans to be maintained. When the value is set to a value that is greater than 0, the container not only pre-populates the MDB bean pool with the specified number, but also attempts to ensure that there are always this many MDB beans in the free pool. This ensures that there are enough MDB beans in the “ready to serve” state to process user requests. This parameter does not guarantee that more than the “steady-pool-size” MDB instances will not exist at a given time. It only governs the number of instances that are pooled over a long period of time. For example, suppose an idle stateless session container has a fully-populated pool with a steady-pool-size of 10. If 20 concurrent requests arrive for the MDB bean component, the container creates 10 additional instances to satisfy the burst of requests. This prevents the container from blocking any of the incoming requests. However, if the activity dies down to 10 or fewer concurrent requests, the additional 10 instances are discarded.	An integer indicating the minimum number of Message Driven Beans (MDBs) to be maintained. The configured default is 10.
Max Pool Size	Specifies the maximum number of MDB beans in the pool.	An integer indicating the maximum number of MDB beans in the pool. A value of 0 means the pool is unbounded. The configured default is 60.
Pool Idle Timeout In Seconds	Specifies the interval at which the “remove expired MDBs” thread runs. This thread periodically removes unused MDB beans with expired timeouts. This provides a hint to the server, and allows the user to specify the maximum amount of time that an MDB bean instance can remain idle in the pool. After this period of time, the pool can remove this bean. When Pool Idle Timeout In Seconds is set to a value greater than 0, the removes or destroys any MDB bean instance that is idle for this specified duration. A value of 0 specifies that idle MDB beans can remain in the pool indefinitely.	An integer indicting the Pool Idle Timeout in seconds for unused MDBs. A value of 0 specifies that idle MDBs can remain in the pool indefinitely. The configured default value is 600.