Hi Guys,

I don’t know is it the right place to ask this question. If not plz forgive
me and direct me to the right place.



I have been struggling for the past two weeks to create a connection pool in
Tomcat 4.x/Tomcat 5.x.

Actually my environment is, Windows XP professional, j2sdk1.4.2_04, Tomcat
5.0.19 and Oracle 8.1.7. I configured

server.xml and web.xml as per the documentation you provided in Apache.org.
But I’m getting the

following error…

SQLException Occured org.apache.commons.dbcp.SQLNestedException: Cannot
create J

DBC driver of class '' for connect URL 'null', cause: null.

NO Suitable driver. I tried all the drivers that are available at Oracle
site and I dropped the jar file in

common\lib directory but of no use. And I tried many ways that are found by
google search.

Please help me out in solving this problem.

Here are the related files….

Server.xml

<!-- Example Server Configuration File -->

<!-- Note that component elements are nested corresponding to their

  parent-child relationships with each other -->



<!-- A "Server" is a singleton element that represents the entire JVM,

  which may contain one or more "Service" instances. The Server

  listens for a shutdown command on the indicated port.



  Note: A "Server" is not itself a "Container", so you may not

  define subcomponents such as "Valves" or "Loggers" at this level.

-->



<Server port="8005" shutdown="SHUTDOWN" debug="0">





<!-- Comment these entries out to disable JMX MBeans support -->

<!-- You may also configure custom components (e.g. Valves/Realms) by

    including your own mbean-descriptor file(s), and setting the

    "descriptors" attribute to point to a ';' seperated list of paths

    (in the ClassLoader sense) of files to add to the default list.

    e.g. descriptors="/com/myfirm/mypackage/mbean-descriptor.xml"

-->

<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"

       debug="0"/>

<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"

       debug="0"/>



<!-- Global JNDI resources -->

<GlobalNamingResources>



  <!-- Test entry for demonstration purposes -->

  <Environment name="simpleValue" type="java.lang.Integer" value="30"/>



  <!-- Editable user database that can also be used by

     UserDatabaseRealm to authenticate users -->

  <Resource name="UserDatabase" auth="Container"

        type="org.apache.catalina.UserDatabase"

    description="User database that can be updated and saved">

  </Resource>

  <ResourceParams name="UserDatabase">

   <parameter>

    <name>factory</name>

    <value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>

   </parameter>

   <parameter>

    <name>pathname</name>

    <value>conf/tomcat-users.xml</value>

   </parameter>

  </ResourceParams>



</GlobalNamingResources>



<!-- A "Service" is a collection of one or more "Connectors" that share

    a single "Container" (and therefore the web applications visible

    within that Container). Normally, that Container is an "Engine",

    but this is not required.



    Note: A "Service" is not itself a "Container", so you may not

    define subcomponents such as "Valves" or "Loggers" at this level.

 -->



<!-- Define the Tomcat Stand-Alone Service -->

<Service name="Catalina">



  <!-- A "Connector" represents an endpoint by which requests are received

     and responses are returned. Each Connector passes requests on to
the

     associated "Container" (normally an Engine) for processing.



     By default, a non-SSL HTTP/1.1 Connector is established on port
8080.

     You can also enable an SSL HTTP/1.1 Connector on port 8443 by

     following the instructions below and uncommenting the second
Connector

     entry. SSL support requires the following steps (see the SSL
Config

     HOWTO in the Tomcat 5 documentation bundle for more detailed

     instructions):

     * If your JDK version 1.3 or prior, download and install JSSE 1.0.2
or

      later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".

     * Execute:

        %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA
(Windows)

        $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA
(Unix)

      with a password value of "changeit" for both the certificate and

      the keystore itself.



     By default, DNS lookups are enabled when a web application calls

     request.getRemoteHost(). This can have an adverse impact on

     performance, so you can disable it by setting the

     "enableLookups" attribute to "false". When DNS lookups are
disabled,

     request.getRemoteHost() will return the String version of the

     IP address of the remote client.

  -->



  <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->

  <Connector port="8080"

         maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

         enableLookups="false" redirectPort="8443" acceptCount="100"

         debug="0" connectionTimeout="20000"

         disableUploadTimeout="true" />

  <!-- Note : To disable connection timeouts, set connectionTimeout value

  to 0 -->

       

       <!-- Note : To use gzip compression you could set the following
properties :

       

                         compression="on"

                         compressionMinSize="2048"

                         noCompressionUserAgents="gozilla,
traviata"


compressableMimeType="text/html,text/xml"

       -->



  <!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->

  <!--

  <Connector port="8443"

         maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

         enableLookups="false" disableUploadTimeout="true"

         acceptCount="100" debug="0" scheme="https" secure="true"

         clientAuth="false" sslProtocol="TLS" />

  -->



  <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->

  <Connector port="8009"

         enableLookups="false" redirectPort="8443" debug="0"

         protocol="AJP/1.3" />



  <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->

  <!-- See proxy documentation for more information about using this. -->

  <!--

  <Connector port="8082"

         maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

         enableLookups="false"

         acceptCount="100" debug="0" connectionTimeout="20000"

         proxyPort="80" disableUploadTimeout="true" />

  -->



  <!-- An Engine represents the entry point (within Catalina) that
processes

     every request. The Engine implementation for Tomcat stand alone

     analyzes the HTTP headers included with the request, and passes
them

     on to the appropriate Host (virtual host). -->



  <!-- You should set jvmRoute to support load-balancing via JK/JK2 ie :

  <Engine name="Standalone" defaultHost="localhost" debug="0"
jvmRoute="jvm1">      

  -->

     

  <!-- Define the top level container in our container hierarchy -->

  <Engine name="Catalina" defaultHost="localhost" debug="0">



   <!-- The request dumper valve dumps useful debugging information about

      the request headers and cookies that were received, and the
response

      headers and cookies that were sent, for all requests received by

      this instance of Tomcat. If you care only about requests to a

      particular virtual host, or a particular application, nest this

      element inside the corresponding <Host> or <Context> entry
instead.



      For a similar mechanism that is portable to all Servlet 2.4

      containers, check out the "RequestDumperFilter" Filter in the

      example application (the source for this filter may be found in

      "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").



      Request dumping is disabled by default. Uncomment the following

      element to enable it. -->

   <!--

   <Valve className="org.apache.catalina.valves.RequestDumperValve"/>

   -->



   <!-- Global logger unless overridden at lower levels -->

   <Logger className="org.apache.catalina.logger.FileLogger"

        prefix="catalina_log." suffix=".txt"

        timestamp="true"/>



   <!-- Because this Realm is here, an instance will be shared globally
-->



   <!-- This Realm uses the UserDatabase configured in the global JNDI

      resources under the key "UserDatabase". Any edits

      that are performed against this UserDatabase are immediately

      available for use by the Realm. -->

   <Realm className="org.apache.catalina.realm.UserDatabaseRealm"

          debug="0" resourceName="UserDatabase"/>



   <!-- Comment out the old realm but leave here for now in case we

      need to go back quickly -->

    <!-- <Realm className="org.apache.catalina.realm.JDBCRealm"
debug="99"

            driverName="oracle.jdbc.driver.OracleDriver"

      connectionURL="jdbc:oracle:oci:@(protected)"/>

      -->



   <!-- Replace the above Realm with one of the following to get a Realm

      stored in a database and accessed via JDBC -->



   <!--

   <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"

        driverName="org.gjt.mm.mysql.Driver"

      connectionURL="jdbc:mysql://localhost/authority"

     connectionName="test" connectionPassword="test"

        userTable="users" userNameCol="user_name"
userCredCol="user_pass"

      userRoleTable="user_roles" roleNameCol="role_name" />

   -->



  <!--

   <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"

        driverName="oracle.jdbc.driver.OracleDriver"

      connectionURL="jdbc:oracle:thin:@(protected)"/>

   

       -->

   <!--

   <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"

        driverName="sun.jdbc.odbc.JdbcOdbcDriver"

      connectionURL="jdbc:odbc:CATALINA"

        userTable="users" userNameCol="user_name"
userCredCol="user_pass"

      userRoleTable="user_roles" roleNameCol="role_name" />

   -->



   <!-- Define the default virtual host

      Note: XML Schema validation will not work with Xerces 2.2.

    -->

   <Host name="localhost" debug="0" appBase="webapps"

    unpackWARs="true" autoDeploy="true"

    xmlValidation="false" xmlNamespaceAware="false">



    <!-- Defines a cluster for this node,

        By defining this element, means that every manager will be
changed.

        So when running a cluster, only make sure that you have webapps
in there

        that need to be clustered and remove the other ones.

        A cluster has the following parameters:



        className = the fully qualified name of the cluster class



        name = a descriptive name for your cluster, can be anything



        debug = the debug level, higher means more output



        mcastAddr = the multicast address, has to be the same for all
the nodes



        mcastPort = the multicast port, has to be the same for all the
nodes



        mcastFrequency = the number of milliseconds in between sending
a "I'm alive" heartbeat



        mcastDropTime = the number a milliseconds before a node is
considered "dead" if no heartbeat is received



        tcpThreadCount = the number of threads to handle incoming
replication requests, optimal would be the same amount of threads as nodes



        tcpListenAddress = the listen address (bind address) for TCP
cluster request on this host,

                    in case of multiple ethernet cards.

                    auto means that address becomes

                    InetAddress.getLocalHost().getHostAddress()



        tcpListenPort = the tcp listen port



        tcpSelectorTimeout = the timeout (ms) for the Selector.select()
method in case the OS

                      has a wakup bug in java.nio. Set to 0 for
no timeout



        printToScreen = true means that managers will also print to
std.out



        expireSessionsOnShutdown = true means that



        useDirtyFlag = true means that we only replicate a session
after setAttribute,removeAttribute has been called.

                  false means to replicate the session after each
request.

                  false means that replication would work for the
following piece of code:

                  <%

                  HashMap map =
(HashMap)session.getAttribute("map");

                  map.put("key","value");

                  %>

        replicationMode = can be either 'pooled', 'synchronous' or
'asynchronous'.

                    * Pooled means that the replication happens
using several sockets in a synchronous way. Ie, the data gets replicated,
then the request return. This is the same as the 'synchronous' setting
except it uses a pool of sockets, hence it is multithreaded. This is the
fastest and safest configuration. To use this, also increase the nr of tcp
threads that you have dealing with replication.

                    * Synchronous means that the thread that
executes the request, is also the

                    thread the replicates the data to the other
nodes, and will not return until all

                    nodes have received the information.

                    * Asynchronous means that there is a specific
'sender' thread for each cluster node,

                    so the request thread will queue the
replication request into a "smart" queue,

                    and then return to the client.

                    The "smart" queue is a queue where when a
session is added to the queue, and the same session

                    already exists in the queue from a previous
request, that session will be replaced

                    in the queue instead of replicating two
requests. This almost never happens, unless there is a

                    large network delay.

    -->        

    <!--

       When configuring for clustering, you also add in a valve to
catch all the requests

       coming in, at the end of the request, the session may or may not
be replicated.

       A session is replicated if and only if all the conditions are
met:

       1. useDirtyFlag is true or setAttribute or removeAttribute has
been called AND

       2. a session exists (has been created)

       3. the request is not trapped by the "filter" attribute



       The filter attribute is to filter out requests that could not
modify the session,

       hence we don't replicate the session after the end of this
request.

       The filter is negative, ie, anything you put in the filter, you
mean to filter out,

       ie, no replication will be done on requests that match one of
the filters.

       The filter attribute is delimited by ;, so you can't escape out
; even if you wanted to.



       filter=".*\.gif;.*\.js;" means that we will not replicate the
session after requests with the URI

       ending with .gif and .js are intercepted.

    -->

   

    <!--

    <Cluster
className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"


managerClassName="org.apache.catalina.cluster.session.DeltaManager"

          expireSessionsOnShutdown="false"

          useDirtyFlag="true">



       <Membership

          className="org.apache.catalina.cluster.mcast.McastService"

          mcastAddr="228.0.0.4"

          mcastPort="45564"

          mcastFrequency="500"

          mcastDropTime="3000"/>



       <Receiver


className="org.apache.catalina.cluster.tcp.ReplicationListener"

          tcpListenAddress="auto"

          tcpListenPort="4001"

          tcpSelectorTimeout="100"

          tcpThreadCount="6"/>



       <Sender


className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"

          replicationMode="pooled"/>



       <Valve
className="org.apache.catalina.cluster.tcp.ReplicationValve"


filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>

    </Cluster>

    -->    







    <!-- Normally, users must authenticate themselves to each web app

        individually. Uncomment the following entry if you would like

        a user to be authenticated the first time they encounter a

        resource protected by a security constraint, and then have that

        user identity maintained across *all* web applications
contained

        in this virtual host. -->

    <!--

    <Valve className="org.apache.catalina.authenticator.SingleSignOn"

            debug="0"/>

    -->



    <!-- Access log processes all requests for this virtual host. By

        default, log files are created in the "logs" directory relative
to

        $CATALINA_HOME. If you wish, you can specify a different

        directory with the "directory" attribute. Specify either a
relative

        (to $CATALINA_HOME) or absolute path to the desired directory.

    -->

    <!--

    <Valve className="org.apache.catalina.valves.AccessLogValve"

          directory="logs" prefix="localhost_access_log."
suffix=".txt"

          pattern="common" resolveHosts="false"/>

    -->



    <!-- Logger shared by all Contexts related to this virtual host. By

        default (when using FileLogger), log files are created in the
"logs"

        directory relative to $CATALINA_HOME. If you wish, you can
specify

        a different directory with the "directory" attribute. Specify
either a

        relative (to $CATALINA_HOME) or absolute path to the desired

        directory.-->

    <Logger className="org.apache.catalina.logger.FileLogger"

          directory="logs" prefix="localhost_log." suffix=".txt"

       timestamp="true"/>



   </Host>

   <Context>

   <Resource name="jdbc/EmployeeDB" auth="Container"

   

           type="javax.sql.DataSource"/>

    <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"

                    driverName="oracle.jdbc.driver.OracleDriver"

      connectionURL="jdbc:oracle:thin:@(protected)"/>

   

    <ResourceParams name="jdbc/EmployeeDB">

   

      <parameter>

   

       <name>user</name>

   

       <value>pricing2_admin</value>

   

      </parameter>

   

      <parameter>

   

       <name>password</name>

   

       <value>pricing2_admin</value>

   

      </parameter>

   

      <parameter>

   

       <name>driverClassName</name>

   

       <value>oracle.jdbc.driver.OracleDriver</value>

   

      </parameter>

   

      <parameter>

   

       <name>url</name>

   

       <value>jdbc:oracle:thin:@(protected)>

   

      </parameter>

   

    </ResourceParams>

    </Context>



  </Engine>



</Service>



</Server>

Web.xml

<?xml version = '1.0' encoding = 'windows-1252'?>

<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">

<web-app>

<description>Empty web.xml file for Web Application</description>

<servlet>

  <servlet-name>Controller</servlet-name>

  <servlet-class>bean.Controller</servlet-class>

</servlet>

<servlet-mapping>

  <servlet-name>Controller</servlet-name>

  <url-pattern>/Controller</url-pattern>

</servlet-mapping>

<session-config>

  <session-timeout>35</session-timeout>

</session-config>

<mime-mapping>

  <extension>html</extension>

  <mime-type>text/html</mime-type>

</mime-mapping>

<mime-mapping>

  <extension>txt</extension>

  <mime-type>text/plain</mime-type>

</mime-mapping>

<welcome-file-list>

  <welcome-file>index.jsp</welcome-file>

  <welcome-file>index.html</welcome-file>

</welcome-file-list>

<resource-ref>



<description>



  Resource reference to a factory for java.sql.Connection



  instances that may be used for talking to a particular



  database that is configured in the server.xml file.



</description>



<res-ref-name>



  jdbc/EmployeeDB



</res-ref-name>



<res-type>



  javax.sql.DataSource



</res-type>



<res-auth>



  Container



</res-auth>



</resource-ref>

</web-app>

Code that I use to get the connection

InitialContext jndiCntx = new InitialContext();

    Context ctx=(Context)jndiCntx.lookup("java:comp/env");

    System.out.println("Looking up jdbc/EmployeeDB");

     DataSource ds =
(javax.sql.DataSource)ctx.lookup("jdbc/EmployeeDB");



    //System.out.println("Got the DataSource......."+ds);

    Connection conn =ds.getConnection();

Its getting executed till displaying the ‘DataSource’

Getting the above error at line

Connection conn =ds.getConnection();

Please let me know the solution.





Thanks

Ram


-----Original Message-----
From: Filip Hanik - Dev [mailto:devlists@(protected)]
Sent: Monday, May 10, 2004 8:43 AM
To: Tomcat Users List
Subject: Re: tomcat clustering

Caused by: java.io.NotSerializableException:


----- Original Message -----
From: "keita elhadji" <keita_elhadji@(protected)>
To: <tomcat-user@(protected)>
Sent: Monday, May 10, 2004 4:52 AM
Subject: tomcat clustering


Hi,

i have a problem with mod_jk2 .
I have two PC with tomcat5.019
1st PC name is : www.avisdunet.biz
2nd PC name is : www1.avisdunet.biz

mod_jk2 and apache2 in the first when i start tomcat
my clustering didn't work and i don't know why and in
my logs catalina.out :

10 mai 2004 11:30:15
org.apache.coyote.http11.Http11Protocol init
INFO: Initialisation de Coyote HTTP/1.1 sur le port
8080
10 mai 2004 11:30:17
org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 48211 ms
10 mai 2004 11:30:22
org.apache.catalina.core.StandardService start
INFO: Démarrage du service Catalina
10 mai 2004 11:30:22
org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.19
10 mai 2004 11:30:23
org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
10 mai 2004 11:30:23
org.apache.catalina.cluster.tcp.SimpleTcpCluster start
INFO: Cluster is about to start
10 mai 2004 11:30:24
org.apache.catalina.cluster.mcast.McastService start
INFO: Sleeping for 2000 secs to establish cluster
membership
10 mai 2004 11:30:26
org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment (
non-jmx )
10 mai 2004 11:30:27
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /pro depuis l'URL
file:/usr/local/java/tomcat/webapps/pro
10 mai 2004 11:30:43
org.apache.catalina.session.StandardManager doLoad
GRAVE: "IOException" lors du chargement des sessions
persistantes: java.io.WriteAbortedException: writing
aborted; java.io.No$
java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:
com.avisdunet.ServeurFond
    at
java.io.ObjectInputStream.readObject0 (ObjectInputStream.java:1278)
    at
java.io.ObjectInputStream.defaultReadFields (ObjectInputStream.java:1845)
    at
java.io.ObjectInputStream.readSerialData (ObjectInputStream.java:1769)
....................................

Caused by: java.io.NotSerializableException:
com.avisdunet.ServeurFond
    at
java.io.ObjectOutputStream.writeObject0 (ObjectOutputStream.java:1054)
    at
java.io.ObjectOutputStream.defaultWriteFields (ObjectOutputStream.java:1332)
    at
java.io.ObjectOutputStream.writeSerialData (ObjectOutputStream.java:1304)
    at
java.io.ObjectOutputStream.writeOrdinaryObject (ObjectOutputStream.java:1247)
    at
java.io.ObjectOutputStream.writeObject0 (ObjectOutputStream.java:1052)
    at
java.io.ObjectOutputStream.defaultWriteFields (ObjectOutputStream.java:1332)
    at
java.io.ObjectOutputStream.writeSerialData (ObjectOutputStream.java:1304)
    at
java.io.ObjectOutputStream.writeOrdinaryObject (ObjectOutputStream.java:1247)

Resolving to alternate DTD
'file:/usr/local/java/jakarta-tomcat-5.0.19/work/Standalone/localhost/pro/lo
ader/org/apache/strut$
Call
org.apache.struts.action.ActionServlet.addServletMapping(monActionServlet/ja
va.lang.String,*.action/java.lang.String)
Call
org.apache.struts.action.ActionServlet.addServletMapping (action/java.lang.St
ring,*.do/java.lang.String)
10 mai 2004 11:30:56
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte depuis l'URL
file:/usr/local/java/jakarta-tomcat-5.0.19/weba$
10 mai 2004 11:30:59
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /balancer depuis l'URL
file:/usr/local/java/jakarta-tomcat-5.$
10 mai 2004 11:31:02
org.apache.catalina.core.StandardContext start
GRAVE: Error filterStart
10 mai 2004 11:31:02
org.apache.catalina.core.StandardContext start
GRAVE: Erreur de démarrage du contexte suite aux
erreurs précédentes
10 mai 2004 11:31:02
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /jsp-examples depuis l'URL
file:/usr/local/java/jakarta-tomca$
10 mai 2004 11:31:09
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /servlets-examples depuis l'URL
file:/usr/local/java/jakarta-$
10 mai 2004 11:31:13
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /tomcat-docs depuis l'URL
file:/usr/local/java/jakarta-tomcat$
10 mai 2004 11:31:15
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /webdav depuis l'URL
file:/usr/local/java/jakarta-tomcat-5.0.$
10 mai 2004 11:31:20
org.apache.coyote.http11.Http11Protocol start
INFO: Démarrage de Coyote HTTP/1.1 sur le port 8080
10 mai 2004 11:31:25
org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
10 mai 2004 11:31:25 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=85/1005
config=/usr/local/java/tomcat/conf/jk2.properties
10 mai 2004 11:31:26
org.apache.catalina.startup.Catalina start
INFO: Server startup in 68992 ms
Lecture fichier :
/usr/local/java/tomcat/webapps/pro/data/spam.txt
<html><body>
CODE=1
</body></html>

thank you for answer






Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout !
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/

Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez
Yahoo! Messenger sur http://fr.messenger.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)