tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Overby" <sove...@solvepoint.com>
Subject Tomcat / Connector failure issues
Date Fri, 13 Oct 2006 13:38:26 GMT
Issues:
 
We've been experiencing some issues with our IIS --> Connector --> Tomcat
setups, 
primarily intermittent 'white pages' where the HTTP response is blank, and
also
this morning an instance where I was forced to restart IIS / IIS admin
service 
in order to get the connection to Tomcat working again, that instance showed
connector log messages of: factory for lb failed for wlb. 
 
Additionally I'm seeing both connector and Tomcat log messages and stack
traces 
that don't seem to manifest a visible problem but are concerning to me. 
 
This email is structured with a layout of our system setup, followed by
examples 
of the log messages of concern, followed by our configuration files. Any
assistance 
in understanding what these log messages mean or any pointers on how to fix
them 
would be most appreciated. 
 
Thanks for your time,
 
Sean Overby
Solvepoint Corporation
 
 
 
System Setup:
 
- Front End:
   Two IIS
      - Web Server 1, IIS 6.0 on Windows 2003, Connector version 1.2.19
      - Web Server 2, IIS 5.x on Windows 2000, Connector version 1.2.19
  
   Web Server 1 and 2 sit inside a DMZ, firewall between both IIS and all
Tomcat Servers.
   
- Back End:
 
  Two Tomcat Servers (in different network segments)
     - Tomcat 1, Tomcat 5.5 on Windows 2003.
     - Tomcat 2, Tomcat 5.5 on Windows 2003.
  
  
Connector Log Messages 
----------------------
 
-- These message corresponded with a complete failure of all servlet
requests with a 
-- 'Page Not Found' error, restarted IIS admin service / IIS website to fix.

[Fri Oct 13 08:04:41 2006] [3620:2044] [error] jk_worker.c (146): factory
for lb failed for wlb
[Fri Oct 13 08:04:41 2006] [3620:2044] [error] jk_worker.c (256): failed to
create worker wlb
[Fri Oct 13 08:22:51 2006] [2812:2300] [error] jk_worker.c (146): factory
for lb failed for wlb
[Fri Oct 13 08:22:51 2006] [2812:2300] [error] jk_worker.c (256): failed to
create worker wlb
[Fri Oct 13 08:28:50 2006] [2348:2164] [error] jk_worker.c (146): factory
for lb failed for wlb
[Fri Oct 13 08:28:50 2006] [2348:2164] [error] jk_worker.c (256): failed to
create worker wlb
 

-- These messages happen intermittently, and do not *seem* to cause any
visible issues
[Fri Oct 13 07:40:44 2006] [0332:2032] [error] jk_ajp_common.c (947):
(wlweb1) can't receive the response message from tomcat, network problems or
tomcat is down (192.168.1.215:8011), err=-54
[Fri Oct 13 07:40:44 2006] [0332:2032] [error] jk_ajp_common.c (1536):
(wlweb1) Tomcat is down or refused connection. No response has been sent to
the client (yet)
[Fri Oct 13 07:40:44 2006] [0332:1796] [error] jk_ajp_common.c (947):
(wlweb1) can't receive the response message from tomcat, network problems or
tomcat is down (192.168.1.215:8011), err=-54
[Fri Oct 13 07:40:44 2006] [0332:1796] [error] jk_ajp_common.c (1536):
(wlweb1) Tomcat is down or refused connection. No response has been sent to
the client (yet)
[Fri Oct 13 07:40:45 2006] [0332:2032] [error] jk_ajp_common.c (1879):
(wlweb1) Connecting to tomcat failed. Tomcat is probably not started or is
listening on the wrong port
[Fri Oct 13 07:40:45 2006] [0332:1796] [error] jk_ajp_common.c (1879):
(wlweb1) Connecting to tomcat failed. Tomcat is probably not started or is
listening on the wrong port
[Fri Oct 13 07:41:44 2006] [0332:2220] [error] jk_ajp_common.c (947):
(wlweb2) can't receive the response message from tomcat, network problems or
tomcat is down (192.168.1.195:8012), err=-54
[Fri Oct 13 07:41:44 2006] [0332:2220] [error] jk_ajp_common.c (1536):
(wlweb2) Tomcat is down or refused connection. No response has been sent to
the client (yet)
[Fri Oct 13 07:41:45 2006] [0332:2220] [error] jk_ajp_common.c (1879):
(wlweb2) Connecting to tomcat failed. Tomcat is probably not started or is
listening on the wrong port
 

Tomcat stdout.log messages:
---------------------------
 
- Interesting thing about this message is that the Tomcat 2 server gets
these
- messages at a rate 50 times higher then on Tomcat 1 server, Tomcat 2 is
also
- on a different LAN segment then Tomcat 1.
 
java.lang.ArrayIndexOutOfBoundsException: 8192
 at org.apache.jk.common.MsgAjp.appendByte(MsgAjp.java:105)
 at org.apache.jk.common.MsgAjp.appendByteChunk(MsgAjp.java:147)
 at org.apache.jk.common.MsgAjp.appendBytes(MsgAjp.java:132)
 at org.apache.jk.common.JkInputStream.appendHead(JkInputStream.java:302)
 at org.apache.jk.core.MsgContext.action(MsgContext.java:258)
 at org.apache.coyote.Response.action(Response.java:182)
 at org.apache.coyote.Response.sendHeaders(Response.java:374)
 at
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:317)
 at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:278)
 at org.apache.catalina.connector.Response.finishResponse(Response.java:483)
 at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
 at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
 at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
 at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
 at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:684)
 at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java
:876)
 at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
 at java.lang.Thread.run(Unknown Source)
 
 
 

Web Server 1, worker.properties:
--------------------------------
 
worker.list=wlb,wlx,jkstatus
 
worker.wlweb1.type=ajp13
worker.wlweb1.host=192.168.1.215
worker.wlweb1.port=8011
worker.wlweb1.socket_keepalive=true
worker.wlweb1.connection_pool_size=600
worker.wlweb1.lbfactor=1
 
worker.wlweb2.type=ajp13
worker.wlweb2.host=192.168.1.195
worker.wlweb2.port=8012
worker.wlweb2.socket_keepalive=true
worker.wlweb2.connection_pool_size=600
worker.wlweb2.connection_pool_timeout=20
worker.wlweb2.lbfactor=1
 
worker.wlxml.type=ajp13
worker.wlxml.host=192.168.1.213
worker.wlxml.port=8009
worker.wlxml.socket_keepalive=true
worker.wlxml.connection_pool_size=600
worker.wlxml.connection_pool_timeout=20
worker.wlxml.lbfactor=1
 
# Defining a load balancer
worker.wlb.type=lb
worker.wlb.balance_workers=wlweb1,wlweb2
 
worker.wlx.type=lb
worker.wlx.balance_workers=wlxml
 
worker.jkstatus.type=status
 

Web Server 1, uriworkermap.properties:
--------------------------------------
# uriworkermap.properties - IIS
/admin/*=wlb
/manager/*=wlb
/jsp-examples/*=wlb
/servlets-examples/*=wlb
/v4/*=wlb
#/r2u/*=wlb
/dhweb/*=wlx 
 
!/servlets-examples/*.jpeg=wlb
 
 
 
Web Server 2, worker.properties:
--------------------------------
worker.list=wlb,jkstatus
 
worker.wlweb1.type=ajp13
worker.wlweb1.host=192.168.1.215
worker.wlweb1.port=8011
worker.wlweb1.socket_keepalive=true
worker.wlweb1.connection_pool_size=600
worker.wlweb1.lbfactor=1
 
worker.wlweb2.type=ajp13
worker.wlweb2.host=192.168.1.195
worker.wlweb2.port=8009
worker.wlweb2.socket_keepalive=true
worker.wlweb2.connection_pool_size=600
worker.wlweb2.lbfactor=1
 
worker.wlb.type=lb
worker.wlb.balance_workers=wlweb1,wlweb2
 
worker.jkstatus.type=status
 
 
 
Web Server 2, uriworkermap.properties:
--------------------------------------
/admin/*=wlb
/manager/*=wlb
/jsp-examples/*=wlb
/servlets-examples/*=wlb
/r2u/*=wlb
 
!/servlets-examples/*.jpeg=wlb
 
 
 
Tomcat Server 1 & 2, server.xml:
-------------------------------
 
- Note with the exception of the line directly below the server.xml is a
- 'vanilla' copy of the install server.xml, the entire server.xml file
- is included below however.
 
  Server 1:
  ---------
    <Connector port="8011" minProcessors="600" maxProcessors="600"
               backlog="300" acceptCount="300" 
               enableLookups="false" redirectPort="8443" protocol="AJP/1.3"
/>
               
  Server 2:
  ---------
    <Connector port="8012" minProcessors="600" maxProcessors="600"
               backlog="300" acceptCount="300" 
               enableLookups="false" redirectPort="8443" protocol="AJP/1.3"
/>
               
               
- Complete 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">
 
  <!-- Comment these entries out to disable JMX MBeans support used for the 
       administration web application -->
  <Listener className="org.apache.catalina.core.AprLifecycleListener" />
  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
/>
  <Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener
className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
 
  <!-- 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"
           factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
          pathname="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="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="8080"               maxHttpHeaderSize="8192"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" redirectPort="8443" acceptCount="100"
               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 HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector port="8443" maxHttpHeaderSize="8192"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" disableUploadTimeout="true"
               acceptCount="100" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->
 
    <!-- Define an AJP 1.3 Connector on port 8009 is default -->
    <!-- ADDED the following parms to this minProcessors="25"
maxProcessors="225" acceptCount="150" - sao -->
    <Connector port="8011" minProcessors="600" maxProcessors="600"
               backlog="300" acceptCount="300" 
               enableLookups="false" redirectPort="8443" 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"
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 AJP ie :
    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">

    --> 
         
    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Catalina" defaultHost="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="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="org.apache.catalina.realm.UserDatabaseRealm"
             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.MemoryRealm" />
      -->
 
      <!-- 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"
             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"
             driverName="oracle.jdbc.driver.OracleDriver"
          connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
         connectionName="scott" connectionPassword="tiger"
              userTable="users" userNameCol="user_name"
userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->
 
      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm"
             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" 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
 
             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
             
             mcastBindAddr = bind the multicast socket to a specific address
             
             mcastTTL = the multicast TTL if you want to limit your
broadcast
             
             mcastSoTimeout = the multicast readtimeout 
 
             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: (only for SimpleTcpReplicationManager)
                            <%
                            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.
            
            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="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 
            and cluster wide
        -->
        
        <!--
        <Cluster
className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
 
managerClassName="org.apache.catalina.cluster.session.DeltaManager"
                 expireSessionsOnShutdown="false"
                 useDirtyFlag="true"
                 notifyListenersOnReplication="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"
                ackTimeout="15000"/>
 
            <Valve
className="org.apache.catalina.cluster.tcp.ReplicationValve"
 
filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>
                   
            <Deployer
className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
                      tempDir="/tmp/war-temp/"
                      deployDir="/tmp/war-deploy/"
                      watchDir="/tmp/war-listen/"
                      watchEnabled="false"/>
        </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" />
        -->
 
        <!-- 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"/>
        -->
 
        <!-- 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="org.apache.catalina.valves.FastCommonAccessLogValve"
                 directory="logs"  prefix="localhost_access_log."
suffix=".txt"
                 pattern="common" resolveHosts="false"/>
        -->
 
      </Host>
 
    </Engine>
 
  </Service>
 
</Server>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message