Run-Time Behavior of Connection Pools in Production Environments

However, when you deploy the adapter in a production environment, set the Minimum Pool Size field to 0 to avoid possible connectivity failures. When the Minimum Pool Size field is set to 1 or greater, and the Siebel Server closes an inactive Siebel connection in its pool, the Siebel Server does not notify the Siebel Adapter that this connection has been closed because the Siebel Server has no knowledge of the Siebel Adapter connection pool. If one of your adapter services uses a connection that the Siebel Servers has closed, that adapter service will fail and you will receive a Siebel disconnect message. To eliminate this potential problem, set the Minimum Pool Size field to 0. In this case, instead of keeping one or more connections open at all times (risking the possibility that the Siebel Server may close its inactive connections), the Siebel Adapter connection pool opens one or more connections as needed, eliminating this possibility. Because the pool reuses connections, performance might not be impacted at all. Remember that the connection pool keeps active all connections that have not exceeded the setting specified for the Expire Timeout field. For example, if you set Expire Timeout to 30000 milliseconds, the pool will retain any inactive connection in the pool for 30 seconds before closing it. Thus, if an adapter service executes at least once every 30 seconds, the same connection will be reused.

Note:
The Expire Timeout interval that you set for the adapter connection must be less than the interval that Siebel's connection pool manager sets for its own connections. For example, if Siebel's connection pool manager sets the interval at 20 seconds and you set the Expire Timeout interval at 30 seconds, then the Siebel connection pool manager will always timeout the connections before the adapter's connection pool does.