Re: Query Executor Problem

Me too. I had the some problem. And couldn't figure out why when I was using tomcat. The point is that the docs at jakarta.apache.org do not really explain the use of the parameters for me. If you use some database as a datasource, the connections will go back into the pool, for a while and get recycled, so you should never call connection.close() when you retrieve a database using a DataSource object from a jndi tree. Just don't forget to set the <maxIdle> parameter to a acceptable high value (higher that the <maxActive> parameter which is the number of connections that are actually opened by tomcat to process any request). This way the connections will get pooled and recycled correctly.

>I had this error as well, and tracked it down to my trying to use a
>Connnection object that had been closed.
>
>-----Original Message-----
>From: pgsql-jdbc-owner(at)postgresql(dot)org
>[mailto:pgsql-jdbc-owner(at)postgresql(dot)org] On Behalf Of Email User
>Sent: Wednesday, November 06, 2002 12:35 AM
>To: daniel(dot)germain(at)gipsynet(dot)com
>Cc: pgsql-jdbc(at)postgresql(dot)org
>Subject: [JDBC] Query Executor Problem
>Hi,
>Our web based application which is using postgresql version 7.1.3
>java.lang.NullPointerException
> at
>org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:61)