In a Microsoft Host Integration Server 2009 or Microsoft Host Integration Server 2010 environment, you configure the Max Pool Size property to specify the maximum number of connections that can exist in the connection pool when connection pooling is enabled for the data source. In this scenario, the Connect Timeout property is not applied correctly when the connection should be available in the pool.
Note This issue only occurs when the system hits the value of the Max Pool Size property, and one connection is queued up.
For example, this problem may occur in the following scenario:
In this scenario, as the third connection is queued up, it should use the available connection out of the pool if the Connect Timeout property has not yet expired. However, in a Host Integration Server 2009 or Host Integration Server 2010 environment, when a queued connection is present, and another open connection is being closed, the third connection does not use the available connection until the connect time out expires. Additionally, you receive the following error message:
Note This issue only occurs when the system hits the value of the Max Pool Size property, and one connection is queued up.
For example, this problem may occur in the following scenario:
- You configure the Max Pool Size property to a value such as "2."
- You open three connections, two are succeeding, and the third is queued up.
- You close one open connection.
In this scenario, as the third connection is queued up, it should use the available connection out of the pool if the Connect Timeout property has not yet expired. However, in a Host Integration Server 2009 or Host Integration Server 2010 environment, when a queued connection is present, and another open connection is being closed, the third connection does not use the available connection until the connect time out expires. Additionally, you receive the following error message:
Failed to get connection from pool
SqlCode=-7049
SqlState=HY000
SqlCode=-7049
SqlState=HY000