2 messages in com.mysql.lists.javaConnection pooling...java.net.BindExc...| From | Sent On | Attachments |
|---|---|---|
| Jon Wilmoth | 20 Oct 2003 16:35 | |
| Jon Wilmoth | 20 Oct 2003 22:47 |
| Subject: | Connection pooling...java.net.BindException: Address already in use error![]() |
|---|---|
| From: | Jon Wilmoth (jonw...@yahoo.com) |
| Date: | 10/20/2003 04:35:03 PM |
| List: | com.mysql.lists.java |
I've been attempting to port an application from Oracle to MySQL for the last few weeks and ran into an unexpected roadblock with Tomcat connection pooling and MySQL. I'm getting the following error from Jakarta Commons DB Connection Pool:
DBCP borrowObject failed: java.sql.SQLException: Unable to connect to any hosts due to exception: java.net.BindException: Address already in use: connect at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:85) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:184) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:722) at org.apache.commons.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:117) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:108) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:312) at com.apex.chronos.app.DatabaseDelegate.getPooledConnection(DatabaseDelegate.java:70) at com.apex.chronos.app.DatabaseDelegate.logConnectionInfo(DatabaseDelegate.java:34) at com.apex.chronos.Startup.testConnectionPool(Startup.java:376) at com.apex.chronos.Startup.init(Startup.java:188) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935)
I've run tests to ensure other clients could connect (i.e. MySQL Control Center, a test java class that does a DriverManager load, etc.) and not had a problem. Thinking the problem was in the jakarta dbcp, I also setup a connection pool definition pointing to the same MySQL db using BEA's Weblogic. This pool implementation was able to successfully perform a "test" sql statement. Has anyone come across this problem before? Is there a way to further trouble shoot the issue inside the driver implementation?
Thanks, Jon




