Hello,
 
I am running Tomcat 4.1.31 at work (dev) and I have a 5.0.28 at home. I have 
been working with Tomcat for quite some time, and ran into a problem trying to 
set up a webapp. At work on my 4.1.31, when  create a new web-app, I edit the 
server.xml file and add my Context (see context below)
 
Anyway when I edit the server.xml on my 5.0.28 I noticed there is no "example 
Context" in which to copy, edit and duplicate. That is how I have always done 
it. Upon reading the docs, it looks like a lot is controlled by web front end. 
Am I correct on this? And if so, where and how do I edit to add Loggers, and 
Resources, etc to it?
 
Or can I just add a new Context somewhere in the server.xml like I used to, and 
if so where in that file (I couldn't find a DTD for server.xml).
 
I get a feeling from the list that I should stay current, but I am having 
trouble understanding the current setups, etc.
 
Thanks for any input.
Sincerely
Scott
 
 
 
 
<Context path="/builder" docBase="builder"
            debug="5" reloadable="true" crossContext="true">
 
             <Logger className="org.apache.catalina.logger.FileLogger"
               prefix="localhost_builder_log." suffix=".txt"
               timestamp="true"/>
 

             <Resource name="jdbc/JNDITestTwo"
               auth="Container"
               type="javax.sql.DataSource"/>
 
             <ResourceParams name="jdbc/JNDITestTwo">
               <parameter>
                 <name>removeAbandoned</name>
                 <value>true</value>
               </parameter>
 
               <parameter>
                 <name>removeAbandonedTimeout</name>
                 <value>60</value>
               </parameter>
 
               <parameter>
                 <name>logAbandoned</name>
                 <value>true</value>
               </parameter>
 
               <parameter>
                 <name>factory</name>
                 <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
               </parameter>
 
               <!-- Maximum number of dB connections in pool. Make sure you
                   configure your mysqld max_connections large enough to handle
                   all of your db connections. Set to 0 for no limit.
               -->
              <parameter>
                <name>maxActive</name>
                <value>100</value>
              </parameter>
 
              <!-- Maximum number of idle dB connections to retain in pool.
                   Set to 0 for no limit.
              -->
             <parameter>
               <name>maxIdle</name>
               <value>30</value>
             </parameter>
 
             <!-- Maximum time to wait for a dB connection to become available
                  in ms, in this example 10 seconds. An Exception is thrown if
                  this timeout is exceeded.  Set to -1 to wait indefinitely.
             -->
            <parameter>
              <name>maxWait</name>
              <value>10000</value>
            </parameter>
 
            <!-- MySQL dB username and password for dB connections  -->
            <parameter>
              <name>username</name>
              <value>spurcell</value>
            </parameter>
 
            <parameter>
              <name>password</name>
              <value>spurcell</value>
            </parameter>
 
            <!-- Class name for mm.mysql JDBC driver -->
            <parameter>
              <name>driverClassName</name>
              <value>org.gjt.mm.mysql.Driver</value>
            </parameter>
 
            <!-- The JDBC connection url for connecting to your MySQL dB.
                 The autoReconnect=true argument to the url makes sure that the
                 mm.mysql JDBC Driver will automatically reconnect if mysqld 
closed the
                 connection.  mysqld by default closes idle connections after 8 
hours.
            -->
            <parameter>
              <name>url</name>
              
<value>jdbc:mysql://localhost:3306/builder?autoReconnect=true</value>
           </parameter>
 
          </ResourceParams>
        </Context>
 
             
 

Reply via email to