On Fri, 2008-01-04 at 10:23 -0600, Caldarale, Charles R wrote: > > From: Scott McClanahan [mailto:[EMAIL PROTECTED] > > Subject: jdbc connection pooling > > > > The developer says that the jar file containing the > > database driver should be published within the web > > applications WEB-INF/lib folder while I say it should > > be in $CATALINA_HOME/common/lib. > > You are correct, the developer is wrong. If Tomcat is to manage the > connections, its internal classes must be able to see the JDBC driver > classes. Look at the classloader hierarchy. > > Note that Tomcat 5.0.x is deprecated; you should be using a newer level. > > > We hoped to define the datasource as a Resource within a > > DefaultContext element in the server.xml so it is available > > to all web applications. > > This is not unusual, although <DefaultContext> is not used in 5.5 and > beyond; there's a context.xml file in the conf directory instead. > > > Also any gotchas to look out for with connection pooling would be > > helpful from those who have actually done it. > > Make sure the webapp code includes finally clauses on all DB access to > make sure the connections are logically closed and thereby returned to > the pool. > > - Chuck > >
I'm going to try my best to not sound ignorant but can you better explain what you mean when you say tomcat "manages" the connections compared to if the application (using the same apache commons projects) were to manage the connections. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
