Bug #29864 connection error lacks connection information

• Submitted: 18 Jul 2007 8:16
• Modified: 18 Jul 2007 13:50
• Reporter: Jan Kneschke
• Status: Won't fix
• Category: Connector / J
• Severity: S4 (Feature request)
• Version: 5.0.4
• OS: Any
• CPU Architecture: Any

[18 Jul 2007 8:16] Jan Kneschke

Description:
When jdbc is used with a connection pool like DBCP from Apache it is hard to find out which connection failed to connect. 

How to repeat:
java.net.SocketException: java.net.ConnectException: Connection refused
        at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
        at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:276)
        at com.mysql.jdbc.Connection.createNewIO(Connection.java:2666)
        at com.mysql.jdbc.Connection.<init>(Connection.java:1531)
        at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
        at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
        at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
...

Suggested fix:
Include the connection DNS|URL into the error-msg.

[18 Jul 2007 13:50] Mark Matthews

As discussed privately, this is information leakage, so we probably shouldn't expose this information.