From tomcat-user-return-124642-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org Mon Apr 11 13:38:12 2005
Return-Path: <tomcat-user-return-124642-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org
Received: (qmail 12967 invoked from network); 11 Apr 2005 13:38:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 11 Apr 2005 13:38:12 -0000
Received: (qmail 49114 invoked by uid 500); 11 Apr 2005 13:37:28 -0000
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 49059 invoked by uid 500); 11 Apr 2005 13:37:27 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 48992 invoked by uid 99); 11 Apr 2005 13:37:26 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from mail.dsg.vertisinc.com (HELO mail.dsg.vertisinc.com) (63.103.126.135)
  by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 11 Apr 2005 06:37:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Subject: RE: DBCP Please Help Get Working Properly
Date: Mon, 11 Apr 2005 08:37:21 -0500
Message-ID: <34385CBC5E8E664EB0007814636AB36A0316D470@exchange1.dimensions.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DBCP Please Help Get Working Properly
Thread-Index: AcU+mP28pe+5bWhOSOes+ClLsgiumQAAd1bA
From: "Scott Purcell" <spurcell@vertisinc.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Thank David for the below information.

This makes some sense, and I will try and make the changes. But this of =
course leads to a follow-up question. Why isn't there any decent =
documentation to get the DBCP running in Tomcat. I am talking about a =
simple example, that explains container versions, jsp versions, possibly =
better ways to use then putting the connection into a JSP page. =
Connecting in a JSP page is just plain dirty, I would like to connect in =
some class where I can call connections from. Does this make sense?

As I mentioned, I followed the example that comes with the documentation =
for my 5.5 Tomcat that displays when you go to localhost.

So, is there any good documentation that shows how to do this, step by =
step?


Thanks,
Scott






-----Original Message-----
From: David Smith [mailto:dns4@cornell.edu]
Sent: Monday, April 11, 2005 8:18 AM
To: Tomcat Users List
Subject: Re: DBCP Please Help Get Working Properly


Ok, define 'no results'. In reality, the naming import isn't the only=20
thing that changed. Your web.xml file *looks* like 2.3 spec from what I=20
can see and you are using JSP 2.x spec syntax in your jsp. If you want=20
the JSP 2.x spec features, you need to declare your web.xml file for=20
servlet 2.4 spec. This should be up at the top of your web.xml (pasted=20
from the specification for servlet 2.4):

<?xml version=3D"1.0" encoding=3D"ISO-8859-1"?>

<web-app xmlns=3D"http://java.sun.com/xml/ns/j2ee"
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation=3D"http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd=94
version=3D=942.4=94>

Then just put all your servlet-mappings, etc., ... after that. The=20
taglib declarations need to be inside a <jsp-config> element for the 2.4 =

spec web.xml file too. That's how I'm guessing you have a 2.3 spec=20
web.xml file. The full spec can be found at=20
http://www.jcp.org/en/jsr/detail?id=3D154

--David

Scott Purcell wrote:

>Hello,
>
>I am trying to use the DBCP features of Tomcat 5.5.7. I created a =
webapp named "testDB" and put it under $CATALINA_HOME/webapps/testDB. =
Then I created a testDB.xml file under =
$CATALINA_HOME/conf/Catalina/localhost/testDB.xml.
>
>// here it is
><Context path=3D"/testDB" docBase=3D"testDB"
>        debug=3D"5" reloadable=3D"true" crossContext=3D"true">
>
>  <Resource name=3D"jdbc/testDB" auth=3D"Container" =
type=3D"javax.sql.DataSource"
>               maxActive=3D"100" maxIdle=3D"30" maxWait=3D"10000"
>               username=3D"javauser" password=3D"javadude" =
driverClassName=3D"com.mysql.jdbc.Driver"
>               =
url=3D"jdbc:mysql://localhost:3306/fritest?autoReconnect=3Dtrue"/>
></Context>
>
>I have been following the notes from:=20
>http://localhost/tomcat-docs/jndi-datasource-examples-howto.html
>
>I made sure I completed the rest of the tasks.
>WEB-INF has the two tag locations, and the resource ref.
>eg:
>
>    <taglib>
>    <taglib-uri>/WEB-INF/sql.tld</taglib-uri>
>    <taglib-location>/WEB-INF/sql.tld</taglib-location>
>    </taglib>
>
>
>    <taglib>
>    <taglib-uri>/WEB-INF/c.tld</taglib-uri>
>    <taglib-location>/WEB-INF/c.tld</taglib-location>
>    </taglib>
>
>  <resource-ref>
>      <description>DB Connection</description>
>      <res-ref-name>jdbc/testDB</res-ref-name>
>      <res-type>javax.sql.DataSource</res-type>
>      <res-auth>Container</res-auth>
>  </resource-ref>
>
>I finally hit my jsp page which is this:
><%@ taglib uri=3D"http://java.sun.com/jsp/jstl/sql" prefix=3D"sql" %>
><%@ taglib uri=3D"http://java.sun.com/jsp/jstl/core" prefix=3D"c" %>
>
><sql:query var=3D"rs" dataSource=3D"jdbc/testDB">
>select id, foo, bar from testdata
></sql:query>
>
><html>
>  <head>
>    <title>DB Test</title>
>  </head>
>  <body>
>
>  <h2>Results</h2>
> =20
><c:forEach var=3D"row" items=3D"${rs.rows}">
>    Foo ${row.foo}<br/>
>    Bar ${row.bar}<br/>
></c:forEach>
>
>
>  </body>
></html>
>
>And I get no results:
>
>Now I am pretty sure I have all configured. Because if I use a fallback =
(Tomcat 4.1) code piece I had, I get results using the same settings:
>
>package foo;
>
>import javax.naming.*;
>import javax.sql.*;
>import java.sql.*;
>
>public class DBTest {
>
>  String foo =3D "Not Connected";
>  int bar =3D -1;
>   =20
>  public void init() {
>    try{
>      Context ctx =3D new InitialContext();
>      if(ctx =3D=3D null )=20
>          throw new Exception("Boom - No Context");
>
>      DataSource ds =3D=20
>            (DataSource)ctx.lookup(
>               "java:comp/env/jdbc/testDB");
>
>      if (ds !=3D null) {
>        Connection conn =3D ds.getConnection();
>             =20
>        if(conn !=3D null)  {
>            foo =3D "Got Connection "+conn.toString();
>            Statement stmt =3D conn.createStatement();
>            ResultSet rst =3D=20
>                stmt.executeQuery(
>                  "select id, foo, bar from testdata");
>            while(rst.next()) {
>               System.out.println("next ....");
>               foo=3Drst.getString(2);
>               bar=3Drst.getInt(3);
>            }
>            conn.close();
>        }
>      }
>    }catch(Exception e) {
>      e.printStackTrace();
>    }
> }
>
> public String getFoo() { return foo; }
> public int getBar() { return bar;}
>}
>
>And using the above class works all day.
>
>The only difference I see is that the class using a "naming" import and =
the jsp does not. Can anyone help.
>
>
>Thanks,
>Scott
>
>
>
>
>
>
>
>
>
>-----Original Message-----
>From: David Smith [mailto:dns4@cornell.edu]
>Sent: Friday, April 08, 2005 1:14 PM
>To: Tomcat Users List
>Subject: Re: Add Context Path, Tomcat 5.5.7
>
>
>Hi.
>
>Take a look at this for where to put <Context> elements:
>http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/context.html
>
>This is new with Tomcat 5.0 and is continued in Tomcat 5.5
>
>--David
>
>Scott Purcell wrote:
>
> =20
>
>>Hello,
>>
>>I am following the information here to add DBCP to my application.
>>http://jakarta.apache.org/tomcat/tomcat-5.5-doc/jndi-datasource-example=
s-howto.html
>>
>>I am reading to add the <Context path=3D"/DBTest ... from the above =
docs." The instructions say to ".
>>
>>Configure the JNDI DataSource in Tomcat by adding a declaration for =
your resource to $CATALINA_HOME/conf/server.xml.
>>
>>Add this in between the </Context> tag of the examples context and the =
</Host> tag closing the localhost definition.
>>
>>
>>
>>So cool, I opened up the server.xml, but do not see any existing =
context or host tags in it. Here is my server.xml file. Does anyone know =
where I put the Context for the DBCP stuff? Thanks,
>>
>>'<!-- 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=3D"8005" shutdown=3D"SHUTDOWN">
>>
>> <!-- Comment these entries out to disable JMX MBeans support used for =
the=20
>>      administration web application -->
>> <Listener =
className=3D"org.apache.catalina.mbeans.ServerLifecycleListener" />
>> <Listener =
className=3D"org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"=
 />
>> <Listener =
className=3D"org.apache.catalina.storeconfig.StoreConfigLifecycleListener=
"/>
>>
>> <!-- Global JNDI resources -->
>> <GlobalNamingResources>
>>
>>   <!-- Test entry for demonstration purposes -->
>>   <Environment name=3D"simpleValue" type=3D"java.lang.Integer" =
value=3D"30"/>
>>
>>   <!-- Editable user database that can also be used by
>>        UserDatabaseRealm to authenticate users -->
>>   <Resource name=3D"UserDatabase" auth=3D"Container"
>>             type=3D"org.apache.catalina.UserDatabase"
>>      description=3D"User database that can be updated and saved"
>>          =
factory=3D"org.apache.catalina.users.MemoryUserDatabaseFactory"
>>         pathname=3D"conf/tomcat-users.xml" />
>>
>> </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=3D"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 HTTP/1.1 Connector on port 8080 -->
>>   <Connector
>>port=3D"80"               maxThreads=3D"150" minSpareThreads=3D"25" =
maxSpareThreads=3D"75"
>>              enableLookups=3D"false" redirectPort=3D"8443" =
acceptCount=3D"100"
>>              connectionTimeout=3D"20000" =
disableUploadTimeout=3D"true" />
>>   <!-- Note : To disable connection timeouts, set connectionTimeout =
value
>>    to 0 -->
>>
>><!-- Note : To use gzip compression you could set the following =
properties :
>>
>>     compression=3D"on"=20
>>     compressionMinSize=3D"2048"=20
>>     noCompressionUserAgents=3D"gozilla, traviata"=20
>>     compressableMimeType=3D"text/html,text/xml"
>>-->
>>
>>   <!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
>>   <!--
>>   <Connector port=3D"8443"=20
>>              maxThreads=3D"150" minSpareThreads=3D"25" =
maxSpareThreads=3D"75"
>>              enableLookups=3D"false" disableUploadTimeout=3D"true"
>>              acceptCount=3D"100" scheme=3D"https" secure=3D"true"
>>              clientAuth=3D"false" sslProtocol=3D"TLS" />
>>   -->
>>
>>   <!-- Define an AJP 1.3 Connector on port 8009 -->
>>   <Connector port=3D"8009"=20
>>              enableLookups=3D"false" redirectPort=3D"8443" =
protocol=3D"AJP/1.3" />
>>
>>   <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
>>   <!-- See proxy documentation for more information about using this. =
-->
>>   <!--
>>   <Connector port=3D"8082"=20
>>              maxThreads=3D"150" minSpareThreads=3D"25" =
maxSpareThreads=3D"75"
>>              enableLookups=3D"false" acceptCount=3D"100" =
connectionTimeout=3D"20000"
>>              proxyPort=3D"80" disableUploadTimeout=3D"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 AJP ie :
>>   <Engine name=3D"Standalone" defaultHost=3D"localhost" =
jvmRoute=3D"jvm1">        =20
>>   -->=20
>>       =20
>>   <!-- Define the top level container in our container hierarchy -->
>>   <Engine name=3D"Catalina" defaultHost=3D"localhost">
>>
>>     <!-- 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=3D"org.apache.catalina.valves.RequestDumperValve"/>
>>     -->
>>
>>     <!-- 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=3D"org.apache.catalina.realm.UserDatabaseRealm"
>>            resourceName=3D"UserDatabase"/>
>>
>>     <!-- Comment out the old realm but leave here for now in case we
>>          need to go back quickly -->
>>     <!--
>>     <Realm className=3D"org.apache.catalina.realm.MemoryRealm" />
>>     -->
>>
>>     <!-- Replace the above Realm with one of the following to get a =
Realm
>>          stored in a database and accessed via JDBC -->
>>
>>     <!--
>>     <Realm  className=3D"org.apache.catalina.realm.JDBCRealm"
>>            driverName=3D"org.gjt.mm.mysql.Driver"
>>         connectionURL=3D"jdbc:mysql://localhost/authority"
>>        connectionName=3D"test" connectionPassword=3D"test"
>>             userTable=3D"users" userNameCol=3D"user_name" =
userCredCol=3D"user_pass"
>>         userRoleTable=3D"user_roles" roleNameCol=3D"role_name" />
>>     -->
>>
>>     <!--
>>     <Realm  className=3D"org.apache.catalina.realm.JDBCRealm"
>>            driverName=3D"oracle.jdbc.driver.OracleDriver"
>>         connectionURL=3D"jdbc:oracle:thin:@ntserver:1521:ORCL"
>>        connectionName=3D"scott" connectionPassword=3D"tiger"
>>             userTable=3D"users" userNameCol=3D"user_name" =
userCredCol=3D"user_pass"
>>         userRoleTable=3D"user_roles" roleNameCol=3D"role_name" />
>>     -->
>>
>>     <!--
>>     <Realm  className=3D"org.apache.catalina.realm.JDBCRealm"
>>            driverName=3D"sun.jdbc.odbc.JdbcOdbcDriver"
>>         connectionURL=3D"jdbc:odbc:CATALINA"
>>             userTable=3D"users" userNameCol=3D"user_name" =
userCredCol=3D"user_pass"
>>         userRoleTable=3D"user_roles" roleNameCol=3D"role_name" />
>>     -->
>>
>>     <!-- Define the default virtual host
>>          Note: XML Schema validation will not work with Xerces 2.2.
>>      -->
>>     <Host name=3D"localhost" appBase=3D"webapps"
>>      unpackWARs=3D"true" autoDeploy=3D"true"
>>      xmlValidation=3D"false" xmlNamespaceAware=3D"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 =3D the fully qualified name of the cluster =
class
>>
>>            name =3D a descriptive name for your cluster, can be =
anything
>>
>>            mcastAddr =3D the multicast address, has to be the same =
for all the nodes
>>
>>            mcastPort =3D the multicast port, has to be the same for =
all the nodes
>>           =20
>>            mcastBindAddr =3D bind the multicast socket to a specific =
address
>>           =20
>>            mcastTTL =3D the multicast TTL if you want to limit your =
broadcast
>>           =20
>>            mcastSoTimeout =3D the multicast readtimeout=20
>>
>>            mcastFrequency =3D the number of milliseconds in between =
sending a "I'm alive" heartbeat
>>
>>            mcastDropTime =3D the number a milliseconds before a node =
is considered "dead" if no heartbeat is received
>>
>>            tcpThreadCount =3D the number of threads to handle =
incoming replication requests, optimal would be the same amount of =
threads as nodes=20
>>
>>            tcpListenAddress =3D the listen address (bind address) for =
TCP cluster request on this host,=20
>>                               in case of multiple ethernet cards.
>>                               auto means that address becomes
>>                               =
InetAddress.getLocalHost().getHostAddress()
>>
>>            tcpListenPort =3D the tcp listen port
>>
>>            tcpSelectorTimeout =3D 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 =3D true means that managers will also print =
to std.out
>>
>>            expireSessionsOnShutdown =3D true means that=20
>>
>>            useDirtyFlag =3D 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: (only for SimpleTcpReplicationManager)
>>                           <%
>>                           HashMap map =3D =
(HashMap)session.getAttribute("map");
>>                           map.put("key","value");
>>                           %>
>>            replicationMode =3D 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=20
>>                              large network delay.
>>       -->            =20
>>       <!--
>>           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=3D".*\.gif;.*\.js;" means that we will not replicate =
the session after requests with the URI
>>           ending with .gif and .js are intercepted.
>>          =20
>>           The deployer element can be used to deploy apps cluster =
wide.
>>           Currently the deployment only deploys/undeploys to working =
members in the cluster
>>           so no WARs are copied upons startup of a broken node.
>>           The deployer watches a directory (watchDir) for WAR files =
when watchEnabled=3D"true"
>>           When a new war file is added the war gets deployed to the =
local instance,
>>           and then deployed to the other instances in the cluster.
>>           When a war file is deleted from the watchDir the war is =
undeployed locally=20
>>           and cluster wide
>>       -->
>>      =20
>>       <!--
>>       <Cluster =
className=3D"org.apache.catalina.cluster.tcp.SimpleTcpCluster"
>>                =
managerClassName=3D"org.apache.catalina.cluster.session.DeltaManager"
>>                expireSessionsOnShutdown=3D"false"
>>                useDirtyFlag=3D"true"
>>                notifyListenersOnReplication=3D"true">
>>
>>           <Membership=20
>>               =
className=3D"org.apache.catalina.cluster.mcast.McastService"
>>               mcastAddr=3D"228.0.0.4"
>>               mcastPort=3D"45564"
>>               mcastFrequency=3D"500"
>>               mcastDropTime=3D"3000"/>
>>
>>           <Receiver=20
>>               =
className=3D"org.apache.catalina.cluster.tcp.ReplicationListener"
>>               tcpListenAddress=3D"auto"
>>               tcpListenPort=3D"4001"
>>               tcpSelectorTimeout=3D"100"
>>               tcpThreadCount=3D"6"/>
>>
>>           <Sender
>>               =
className=3D"org.apache.catalina.cluster.tcp.ReplicationTransmitter"
>>               replicationMode=3D"pooled"
>>               ackTimeout=3D"15000"/>
>>
>>           <Valve =
className=3D"org.apache.catalina.cluster.tcp.ReplicationValve"
>>                  =
filter=3D".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>
>>                 =20
>>           <Deployer =
className=3D"org.apache.catalina.cluster.deploy.FarmWarDeployer"
>>                     tempDir=3D"/tmp/war-temp/"
>>                     deployDir=3D"/tmp/war-deploy/"
>>                     watchDir=3D"/tmp/war-listen/"
>>                     watchEnabled=3D"false"/>
>>       </Cluster>
>>       -->       =20
>>
>>
>>
>>       <!-- 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=3D"org.apache.catalina.authenticator.SingleSignOn" />
>>       -->
>>
>>       <!-- 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=3D"org.apache.catalina.valves.AccessLogValve"
>>                directory=3D"logs"  prefix=3D"localhost_access_log." =
suffix=3D".txt"
>>                pattern=3D"common" resolveHosts=3D"false"/>
>>       -->
>>
>>       <!-- 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.
>>            This access log implementation is optimized for maximum =
performance,
>>            but is hardcoded to support only the "common" and =
"combined" patterns.
>>       -->
>>       <!--
>>       <Valve =
className=3D"org.apache.catalina.valves.FastCommonAccessLogValve"
>>                directory=3D"logs"  prefix=3D"localhost_access_log." =
suffix=3D".txt"
>>                pattern=3D"common" resolveHosts=3D"false"/>
>>       -->
>>
>>     </Host>
>>
>>   </Engine>
>>
>> </Service>
>>
>></Server>
>>
>>
>>
>>
>>
>>
>>Scott K Purcell | Developer | VERTIS |=20
>>555 Washington Ave. 4th Floor | St. Louis, MO 63101 |=20
>>314.588.0720 Ext:1320 | spurcell@vertisinc.com | =
http://www.vertisinc.com <http://www.vertisinc.com/> =20
>>
>>Vertis is the premier provider of targeted advertising, media, and=20
>>marketing services that drive consumers to marketers more effectively. =

>>                                               =20
>>
>>
>>
>>=20
>>
>>   =20
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
> =20
>



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org