tomcat-taglibs-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Shead <>
Subject RE: DBTags and Poolman
Date Wed, 19 Sep 2001 15:46:24 GMT
My understanding of connection pooling (and I welcome any corrections if I'm
wrong) is:

If you are using a JDBC 2.0 driver and you give JNDI a handle to a
connection to the database and have the DBTags get their connection info
from JNDI, then JDBC will automatically pool the connections.  


-----Original Message-----
From: Wim Bervoets []
Sent: Wednesday, September 19, 2001 5:38 AM
To: ''
Subject: DBTags and Poolman


I have a few questions about DBTags:

1) I open a connection and close a connection in each jsp that accesses the
I'm using the latest mysql JDBC driver.... is there connection pooling built
in in that driver or not ?

2) I have tried to use DBTags and Poolman together but it didn't work... Did
someone already do this and what were the results.

this is in my web.xml :

        Which Database to access and where it is located
        JDBC Driver
        DB user id
        DB password

This in my jsp:

<sql:connection id="conn1">
  <sql:url initParameter="dbURL"/> 
  <sql:driver initParameter="mysqlDriver"/>
  <sql:userId initParameter="dbUserId"/> 
  <sql:password initParameter="dbPassword"/>

and this in the poolman.xml file: 

<?xml version="1.0" encoding="UTF-8"?>



  <!-- ========================================================== -->
  <!-- These entries are an example of JDBC Connection pooling.   -->
  <!-- Many of the parameters are optional. Consult the           -->
  <!-- UsersGuide.html doument and the poolman.xml.template file  -->
  <!-- for guidance and element definitions.                      -->
  <!-- ========================================================== -->


    <!-- ============================== -->
    <!-- Physical Connection Attributes -->
    <!-- ============================== -->

    <!-- Standard JDBC Driver info -->





    <!-- Query Cache Attributes-->





View raw message