>> 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. -- View this message in context: http://www.nabble.com/How-to-turn-off-JNDI-datasource-connection-pooling-tp21490681p21507284.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
