[
https://issues.apache.org/jira/browse/DBCP-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated DBCP-205:
-----------------------------
Fix Version/s: 1.3
Affects Version/s: (was: 1.2.1)
(was: Nightly Builds)
1.2.2
Moving this to 1.3 fix version - though I don't know if this is something that
we can fix in dbcp. It does not look like the actual bug report ed is
DBCP-related. More likely this is the result of heavy socket open/close
activity when a loaded server is trying to keep maxIdle very low. What is
really being requested here is an adaptive / more advanced pool management
capability - create headroom during loaded periods, but then quiesce when load
abates.
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
https://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]
