Use Torque.closeConnection() (as in the example below).
Connection con = Torque.getConnection();
Statement stmt = con.createStatement();
ResultSet r = stmt.executeQuery("select name from
custmers");
while (r.next()) {
String name = r.getString("name");
}
r.close();
stmt.close();
Torque.closeConnection(con);
Ilan
> -----Original Message-----
> From: Eric Lalande [mailto:[EMAIL PROTECTED]
> Sent: 10 June 2004 09:58
> To: [EMAIL PROTECTED]
> Subject: Connection Pool Problem
>
>
> I am using the Torque connection pool with Postgresql 7.3 on jvm 1.4 and
> Redhat 9. I have set the number of defaultMaxConnections to 32 and the
> postgresql max_connections to 100 as well as setting the
> shared_buffers to
> 200. This is for test - I wanted the postgres number to be higher than
> the torque number.
>
> After putting a load on this the connections in the torque
> connection pool
> will grow to 100 eventually running out of available connections.
>
> Also this is torque 3.1 and the application is on Turbine 2.2.
>
> Thanks in advance to anyone who can help me out.
>
> Eric
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
