Thanks,
that really helped.
David Smith-2 wrote:
>
> Yes, remove all copies except one and that one should be in the
> common/lib directory. It has to be in common/lib to essentially be
> visible to both tomcat internal code as well as all the webapps. There
> can't be a copy anywhere else
David Smith wrote:
Yes, remove all copies except one and that one should be in the
common/lib directory. It has to be in common/lib to essentially be
visible to both tomcat internal code as well as all the webapps. There
can't be a copy anywhere else in tomcat because ... well I'll let
Yes, remove all copies except one and that one should be in the
common/lib directory. It has to be in common/lib to essentially be
visible to both tomcat internal code as well as all the webapps. There
can't be a copy anywhere else in tomcat because ... well I'll let
the classloader how-
No,
I have commons-dbcp.1.2.2 jar in the lib directory of all of my web app as
well.
Should I remove the commons-dbcp1.2.2.jar from the web apps
and put the jar files in the common/lib directory.
The jar files are:
commons-dbcp-1.2.2
commons-pool-1.3
I assume that the naming-factory-dbcp.jar t
When getting the DataSource (Or BasicDataSource in my case) from tomcat's
JNDI/JDBC service
does Tomcat manage the connection pooling itself.
Essentially yes. You still have to be sure you close your database
objects, but the rest is done by DBCP.
Do I just need to retrieve the DataSource a
I have configured my web app to use tomcat's connection pooling.
and also I have modfied the default value of the factory attribute:
factory="org.apache.commons.dbcp.BasicDataSourceFactory"
Here is the context.xml
Here is how I retrieve the data source so that I later can ask for a
