Thanks Jan. I don't want to use Tomcat's database pool, I just want to be
able to define the datasource using JNDI so it is external to my
application. I am doing this for various web servers and I'm beginning to
think I will have to tell my customers Tomcat does not support JNDI
datasource defini
I am managing the database connection credentials because this is the only
way to access this legacy database. Otherwise I have very little code
because Hibernate takes care of all the heavy lifting. As part of the
deployment I just need a way of defining the datasource in a manner that is
externa
>> 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 perform
Apologies if I don't understand how a jndi datasource should work or if I've
not provided enough explanation but what I want is for Tomcat to keep out of
connection creation. Even if I have maxactive set to 1 I still get a
stacktrace like this,
at
org.apache.tomcat.dbcp.dbcp.DriverConnectionFacto
Thanks Chuck. I've uploaded it again, this time as a text file. It seems ok
this time.
On Thu, Jan 15, 2009 at 7:02 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Keith Thomas [mailto:keith.tho...@gmail.com]
> > Subject: How to turn off JNDI dataso
I have an application that runs against a legacy database. For reasons I
won't go into here I need to turn off jndi datasource connection pooling. I
have been unsuccessful finding documentation or mailing list entries on how
to do this.
I am running Tomcat 6.0.18 as a service on Win XP against a
