Configuring Java CAPS Environment Components for Communications Adapters

HL7 Inbound Adapter - MDB Pool Settings

The HL7 Inbound Adapter - MDB Pool Settings are specific to the MDB bean pool of Sun Java System Application Server or Sun Runtime Server only. The parameter settings in this section will go into sun-ejb-jar.xml.

This section of the TCP/IP HL7 Adapter Environment properties contains the top-level parameters displayed in the following table.

Table 9 Environment - HL7 Inbound Adapter - TCPIP Inbound Settings

Name 

Description 

Required Value 

Steady Pool Size

Specifies the minimum number of MDB beans to be maintained. 

When the value is set to a number greater than 0 (zero), the container not only pre-populates the MDB bean pool with the specified number, but also attempts to ensure that there is 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 necessarily guarantee that no more than steady-pool-size instances 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. The advantage of this is that it 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 indication the minimum number of MDB beans to be maintained. 

The configured default is 10.

Max Pool Size

Specifies the maximum number of MDB beans in the pool. 

An integer indication the maximum number of MDB beans in the pool. A value of 0 (zero) indicates that the pool is unbounded.

The configured default is 60.

Pool Idle Timeout in Seconds

Specifies the maximum amount of time (in seconds) that an MDB bean instance can remain idle in the pool. When an MDB has exceeded the configured Pool Idle Timeout, a timer thread removes the unused MDB bean. This property defines the interval at which this thread runs. 

A value greater than 0 indicates that the container removes or destroys any MDB bean instance that is idle at this specified duration. A value of 0 (zero) specifies that idle MDB beans can remain in the pool indefinitely. 

The maximum amount of time (in seconds) that an MDB bean instance can remain idle in the pool. 

The configured default is 600 (10 minutes).