PostgreSQL/Tomcat JNDI Datasource Questions
От
Warren Killian
Тема
PostgreSQL/Tomcat JNDI Datasource Questions
Дата
Msg-id
42828CF9.5070008@comcast.net
Список
Дерево обсуждения
PostgreSQL/Tomcat JNDI Datasource Questions Warren Killian <warrenk19@comcast.net>
Re: PostgreSQL/Tomcat JNDI Datasource Questions Dave Cramer <pg@fastcrypt.com>
Re: PostgreSQL/Tomcat JNDI Datasource Questions Warren Killian <warrenk19@comcast.net>
Re: PostgreSQL/Tomcat JNDI Datasource Questions Dave Cramer <pg@fastcrypt.com>
Re: PostgreSQL/Tomcat JNDI Datasource Questions David Gagnon <dgagnon@siunik.com>
Re: PostgreSQL/Tomcat JNDI Datasource Questions David Gagnon <dgagnon@siunik.com>
Hello group,
I have several questions concerning configuring and using a JNDI DataSource
with PostgreSQL and Apache Tomcat. Currently I have
successfully configured a "basic" DataSource. Currently, my configuration
which resides in a context.xml file is as follows:
factory
org.apache.commons.dbcp.BasicDataSourceFactory
driverClassName
org.postgresql.Driver
url
jdbc:postgresql://myIP/test
username
Whoopie
password
Doopie
removeAbandoned
true
removeAbandonedTimeout
20
maxWait
5000
maxActive
5
maxIdle
2
validationQuery
SELECT * FROM test
Using the above configuration, my JSP pages can connect to PostgreSQL and
perform all required database operations.
But all is not right! I have the following issues:
1.) Connections are NEVER closed
Say I hit my JSP page which perform a query and display the results.
Using netstat I can see that one connection to PostgreSQL has been
established. But then, if I uninstall and reinstall my web app and hit my
JSP page again, then the output of "netstat -p -t" shows that a second
connection to PostgreSQL is established.
The first connection never goes away! If I continue to
uninstall/reinstall/hit JSP page, the connections continue to acrue and
never go away. The number of connections can even exceed the value of
"maxActive" defined in my context.xml file. What am I doing wrong?
2.) Idle connections aren't closed
As mentioned above, the connections which are opened by my web app are
kept around forever and never closed. In my context.xml file above, I've
defined the "removeAbandoned" parameter to true and have set the
"removeAbandonedTimeout" parameter to 20 seconds. But the connections are
never closed. Every time I run "netstat -p -t", the connections are
still there. :(
3.) Is my configuration correct for performing Pooling?
I "can" get "a" database connection using this configuration. But is this
adequate to perform connection pooling? How can I tell if/when connection
pooling is actually being performed correctly?
Any help would be greatly appreciated.
--
Thank you,
Warren Killian
warrenk19@comcast.net
Q: How many Zen masters does it take to screw in a light bulb?
A: None. The universe spins the bulb and the Zen master stays out
of the way.
В списке pgsql-jdbc по дате отправления