You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2007/01/26 01:55:49 UTC
[jira] Commented: (DBCP-205) Intermittently getting "Could not
retrieve connection info from pool" when under load
[ https://issues.apache.org/jira/browse/DBCP-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467713 ]
Henri Yandell commented on DBCP-205:
------------------------------------
Agreed - seems to be that the JDBC driver/db just doesn't like the amount of activity.
Not that I grok how the driver could be running out of client side ports to connect from; there're tons of those aren't there?
Might be a SQL Server driver specific bit I guess if it's trying to define the actual port to connect from and it's getting screwed up for some reason.
> Intermittently getting "Could not retrieve connection info from pool" when under load
> -------------------------------------------------------------------------------------
>
> Key: DBCP-205
> URL: https://issues.apache.org/jira/browse/DBCP-205
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.2.2
> 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
> Fix For: 1.3
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org