Dear Keith,
It's not clear what you want to do (as opposed to what you don't
want to
do). Is your goal to use a >> new DB connection for every DB access
your
webapp makes, or do you want to do DB connection >>
pooling inside your webapp, or ???
Not using connection pooling at all is a real performance killer.
- Chuck
The security for the data within the database is entirely baked into
the
restriction that every user has their own database connection. As
far as I
can tell it is not possible to use connection pooling a retain
secure access
to the data without an awful lot of re-work.
At the moment I am using a new DB connection for every DB access my
app
makes. Later I may implement my own database polling but either way
it will
be my code initiating connection requests not Tomcat's.
Setting maxactive to zero stops exceptions but the app just seems to
be
hanging.
Two options that I see:
1) Why are you still using Tomcat's pool at all? Just create your own
connections in the code. Instead of each lookup just do the old
"driver.createConnection()" etc. Where driver is some static somewhere.
2) Write a trivial connection pool and drop it into the Tomcat lib.
Use the new Tomcat JDBC pool code as a starting point.
--
Kees Jan
http://java-monitor.com/forum/
kjkos...@kjkoster.org
06-51838192
The secret of success lies in the stability of the goal. -- Benjamin
Disraeli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
