From: | Daniele Depetrini <daniele(dot)depetrini(at)criticalpath(dot)net> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Pooled connections idle timeout |
Date: | 2008-08-18 22:09:26 |
Message-ID: | 48A9F316.60305@criticalpath.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi Again,
Any ideas?
Daniele.
Daniele Depetrini wrote:
> Hi All,
>
> I'm running JDBC 8.3-603 drivers against PG server 8.3.3. I'm using
> JDBC3.0 API with connection pooling. Here my pool init code:
>
> pool = new Jdbc3PoolingDataSource();
> pool.setDataSourceName("DB");
> pool.setServerName(servername);
> pool.setDatabaseName(db);
> pool.setUser(user);
> pool.setPassword(password);
> pool.setPortNumber(port);
> pool.setMaxConnections(maxConn);
>
> Connections are opened and closed via conn=pool.getConnection() /
> conn.close().
>
> I've noted that once a connection get opened since needed, it's never
> really closed, application and database stay connected up to restart.
> Since I'm writing a java server application, my application will
> eventually stay up for a long time and spike of traffics can open a
> lot of connectoins to PG that will never be released, even in low
> traffic time.
>
> Is there any auto-idle-close mechanism, either client or server level?
>
> Thanks in advance,
>
> Daniele.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2008-08-18 22:24:15 | Re: Pooled connections idle timeout |
Previous Message | Oliver Jowett | 2008-08-18 21:58:38 | Re: Hint: parseSql(...) in AbstractJdbc2Statement.java can be optimized performance-wise |