[ 
http://issues.apache.org/jira/browse/DBCP-205?page=comments#action_12457739 ] 
            
Rida Ligurs commented on DBCP-205:
----------------------------------

Hi Phil,

Thanks for your response.  I tried your suggestion of increasing maxIdle
to 10 and it worked.  I really didn't want to have 10 connections
sitting idle.  Is this a bug?  In my case, under regular load it only
gets to a maximum of 4 or 5 active connections.  For those rare
instances where there are significantly more active connections, I would
want them to be release as soon as they are no longer needed.

Rida




> Intermittently getting "Could not retrieve connection info from pool" when 
> under load
> -------------------------------------------------------------------------------------
>
>                 Key: DBCP-205
>                 URL: http://issues.apache.org/jira/browse/DBCP-205
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.1, Nightly Builds
>         Environment: JRE 1.4.2_03, commons_dbcp20061206, commons-pool-1.2, 
> Microsoft SQL Server 2005 JDBC Driver (sqljdbc_1.0.809.102)
>            Reporter: Rida Ligurs
>
>  I have a Tomcat servlet that uses a connection pool with the following 
> settings:
> MaxActive=30
> MaxIdle=3
> MaxWait=50000 milliseconds
> IdleTimeOut=3600 seconds
> LoginTimeOut=100 seconds
> TimeBetweenEvictionRunsMills=-1
> Under load, I get the following exception:
> org.apache.commons.dbcp.SQLNestedException: Could not retrieve connection 
> info from pool
>       at 
> org.apache.commons.dbcp.datasources.SharedPoolDataSource.getPooledConnectionAndInfo(SharedPoolDataSource.java:171)
>       at 
> org.apache.commons.dbcp.datasources.InstanceKeyDataSource.getConnection(InstanceKeyDataSource.java:662)
>       at 
> org.apache.commons.dbcp.datasources.InstanceKeyDataSource.getConnection(InstanceKeyDataSource.java:646)
> Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP 
> connection to the host  has failed. java.net.BindException: Address already 
> in use: connect
>       at 
> com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown 
> Source)
>       at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown 
> Source)
>       at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
>       at java.sql.DriverManager.getConnection(Unknown Source)
>       at java.sql.DriverManager.getConnection(Unknown Source)
>       at 
> org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.getPooledConnection(DriverAdapterCPDS.java:177)
>       at 
> org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.getPooledConnection(DriverAdapterCPDS.java:132)
>       at 
> org.apache.commons.dbcp.datasources.KeyedCPDSConnectionFactory.makeObject(KeyedCPDSConnectionFactory.java:158)
>       at 
> org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:747)
>       at 
> org.apache.commons.dbcp.datasources.SharedPoolDataSource.getPooledConnectionAndInfo(SharedPoolDataSource.java:167)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to