Matthew Storer wrote:
> To start, I'm putting together a Java client-server app, where the
> server side talks to a PostgreSQL database via an Apache Commons DBCP
> link for connection pooling. Using the code I've included below, I'm
> able to establish a connection, get database metadata, and execute
> stored functions perfectly well PROVIDING I DON'T try to call
> getConnection() again without closing the first connection beforehand.
> (but it seems to me that doing that ought to work alright, because if I
> call getConnection() a second time, shouldn't the DBCP code just pull a
> new connection from the pool, and not, instead, throw this exception?)
Can you reduce it to a self-contained test case? That way others can
test and help with it as well.
> EXCEPTION:
> ----------
> org.postgresql.util.PSQLException: Something unusual has occured to
> cause the driver to fail. Please report this exception.
> at org.postgresql.Driver.connect(Driver.java:276)
> at java.sql.DriverManager.getConnection(Unknown Source)
> at java.sql.DriverManager.getConnection(Unknown Source)
> at
>
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:68)
> at
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
> at
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:840)
> at
> org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:176)
>
> at java.sql.DriverManager.getConnection(Unknown Source)
> at java.sql.DriverManager.getConnection(Unknown Source)
> at
> myproject.db.ConnectionPool.getConnection(ConnectionPool.java:136)
Is that the whole stack trace? The stack trace of the underlying
exception should be there as well.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
