You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Mon Cab <fu...@yahoo.com> on 2010/03/26 01:30:38 UTC
Why is tomcat taking so long to start?
Tomcat is taking 3 mins to start up, while it used to start up in a matter of seconds.
We have 2 containers set up with 7-9 hosts configured, each with its own docbase directory.
Looking at the working directory, it seems that there is a directory for each host and for some
unknown reason within that directory there are directories for each of the other hosts docbases
ie.
work
|
|-catalina
-- domain1.com
|
|- docbase for domain1
|- docbase for domain 2
...
-- docbase for domain7
-- domain2.com
|
|- docbase for domain1
|- docbase for domain 2
...
-- docbase for domain7
Is this supposed to happen?
I included the catalina log file below, and the server-conf file below that.
Mar 25, 2010 4:30:53 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-216.55.168.27-8080
Mar 25, 2010 4:30:54 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8443
Mar 25, 2010 4:30:54 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-66.226.76.184-8080
Mar 25, 2010 4:30:54 PM org.apache.coyote.http11.Http11Protocol init
SEVERE: Error initializing endpoint
java.net.BindException: Address already in use:8443
at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:264)
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:137)
at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1429)
at org.apache.catalina.core.StandardService.initialize(StandardService.java:609)
at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:2384)
at org.apache.catalina.startup.Catalina.load(Catalina.java:507)
at org.apache.catalina.startup.Catalina.load(Catalina.java:528)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:250)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:424)
Mar 25, 2010 4:30:54 PM org.apache.catalina.startup.Catalina load
SEVERE: Catalina.start
LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use:8443
at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1431)
at org.apache.catalina.core.StandardService.initialize(StandardService.java:609)
at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:2384)
at org.apache.catalina.startup.Catalina.load(Catalina.java:507)
at org.apache.catalina.startup.Catalina.load(Catalina.java:528)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:250)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:424)
Mar 25, 2010 4:30:54 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 4047 ms
Mar 25, 2010 4:30:54 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina1
Mar 25, 2010 4:30:54 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.28
Mar 25, 2010 4:30:54 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
log4j:INFO Using URL [file:/usr/share/tomcat5.0/common/classes/log4j.xml] for automatic log4j configuration of repository named [default].
Mar 25, 2010 4:30:59 PM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Mar 25, 2010 4:30:59 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp2 from URL file:/usr/share/tomcat5.0/webapps/datingapp2
Mar 25, 2010 4:31:02 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp from URL file:/usr/share/tomcat5.0/webapps/datingapp
Mar 25, 2010 4:31:03 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech2 from URL file:/usr/share/tomcat5.0/webapps/tech2
Mar 25, 2010 4:31:04 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech from URL file:/usr/share/tomcat5.0/webapps/tech
Mar 25, 2010 4:31:06 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech0 from URL file:/usr/share/tomcat5.0/webapps/tech0
Mar 25, 2010 4:31:07 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /webdav from URL file:/usr/share/tomcat5.0/webapps/webdav
Mar 25, 2010 4:31:07 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /basementbeat1 from URL file:/usr/share/tomcat5.0/webapps/basementbeat1
Mar 25, 2010 4:31:08 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp3 from URL file:/usr/share/tomcat5.0/webapps/datingapp3
Mar 25, 2010 4:31:11 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /basementbeat0 from URL file:/usr/share/tomcat5.0/webapps/basementbeat0
Mar 25, 2010 4:31:13 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingdirectory from URL file:/usr/share/tomcat5.0/webapps/datingdirectory
Mar 25, 2010 4:31:15 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Mar 25, 2010 4:31:16 PM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Mar 25, 2010 4:31:16 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp2 from URL file:/usr/share/tomcat5.0/webapps/datingapp2
Mar 25, 2010 4:31:19 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp from URL file:/usr/share/tomcat5.0/webapps/datingapp
Mar 25, 2010 4:31:21 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech2 from URL file:/usr/share/tomcat5.0/webapps/tech2
Mar 25, 2010 4:31:23 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech from URL file:/usr/share/tomcat5.0/webapps/tech
Mar 25, 2010 4:31:25 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech0 from URL file:/usr/share/tomcat5.0/webapps/tech0
Mar 25, 2010 4:31:27 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /webdav from URL file:/usr/share/tomcat5.0/webapps/webdav
Mar 25, 2010 4:31:28 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /basementbeat1 from URL file:/usr/share/tomcat5.0/webapps/basementbeat1
Mar 25, 2010 4:31:30 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp3 from URL file:/usr/share/tomcat5.0/webapps/datingapp3
Mar 25, 2010 4:31:34 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /basementbeat0 from URL file:/usr/share/tomcat5.0/webapps/basementbeat0
Mar 25, 2010 4:31:35 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingdirectory from URL file:/usr/share/tomcat5.0/webapps/datingdirectory
Mar 25, 2010 4:31:36 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Mar 25, 2010 4:31:38 PM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Mar 25, 2010 4:31:38 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp2 from URL file:/usr/share/tomcat5.0/webapps/datingapp2
Mar 25, 2010 4:31:40 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp from URL file:/usr/share/tomcat5.0/webapps/datingapp
Mar 25, 2010 4:31:40 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech2 from URL file:/usr/share/tomcat5.0/webapps/tech2
Mar 25, 2010 4:31:41 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech from URL file:/usr/share/tomcat5.0/webapps/tech
Mar 25, 2010 4:31:42 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech0 from URL file:/usr/share/tomcat5.0/webapps/tech0
Mar 25, 2010 4:31:43 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /webdav from URL file:/usr/share/tomcat5.0/webapps/webdav
Mar 25, 2010 4:31:43 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /basementbeat1 from URL file:/usr/share/tomcat5.0/webapps/basementbeat1
Mar 25, 2010 4:31:44 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp3 from URL file:/usr/share/tomcat5.0/webapps/datingapp3
Mar 25, 2010 4:31:46 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /basementbeat0 from URL file:/usr/share/tomcat5.0/webapps/basementbeat0
Mar 25, 2010 4:31:46 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingdirectory from URL file:/usr/share/tomcat5.0/webapps/datingdirectory
Mar 25, 2010 4:31:48 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Mar 25, 2010 4:31:49 PM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Mar 25, 2010 4:31:49 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp2 from URL file:/usr/share/tomcat5.0/webapps/datingapp2
Mar 25, 2010 4:31:51 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp from URL file:/usr/share/tomcat5.0/webapps/datingapp
Mar 25, 2010 4:31:51 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech2 from URL file:/usr/share/tomcat5.0/webapps/tech2
Mar 25, 2010 4:31:52 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech from URL file:/usr/share/tomcat5.0/webapps/tech
Mar 25, 2010 4:31:53 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech0 from URL file:/usr/share/tomcat5.0/webapps/tech0
Mar 25, 2010 4:31:54 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /webdav from URL file:/usr/share/tomcat5.0/webapps/webdav
Mar 25, 2010 4:31:54 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /basementbeat1 from URL file:/usr/share/tomcat5.0/webapps/basementbeat1
Mar 25, 2010 4:31:55 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp3 from URL file:/usr/share/tomcat5.0/webapps/datingapp3
Mar 25, 2010 4:31:57 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /basementbeat0 from URL file:/usr/share/tomcat5.0/webapps/basementbeat0
Mar 25, 2010 4:31:57 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingdirectory from URL file:/usr/share/tomcat5.0/webapps/datingdirectory
Mar 25, 2010 4:31:59 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Mar 25, 2010 4:32:01 PM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Mar 25, 2010 4:32:01 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp2 from URL file:/usr/share/tomcat5.0/webapps/datingapp2
Mar 25, 2010 4:32:03 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp from URL file:/usr/share/tomcat5.0/webapps/datingapp
Mar 25, 2010 4:32:03 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech2 from URL file:/usr/share/tomcat5.0/webapps/tech2
Mar 25, 2010 4:32:04 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech from URL file:/usr/share/tomcat5.0/webapps/tech
Mar 25, 2010 4:32:05 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tech0 from URL file:/usr/share/tomcat5.0/webapps/tech0
Mar 25, 2010 4:32:06 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /webdav from URL file:/usr/share/tomcat5.0/webapps/webdav
Mar 25, 2010 4:32:06 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /basementbeat1 from URL file:/usr/share/tomcat5.0/webapps/basementbeat1
Mar 25, 2010 4:32:07 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingapp3 from URL file:/usr/share/tomcat5.0/webapps/datingapp3
Mar 25, 2010 4:32:09 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /basementbeat0 from URL file:/usr/share/tomcat5.0/webapps/basementbeat0
Mar 25, 2010 4:32:10 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /datingdirectory from URL file:/usr/share/tomcat5.0/webapps/datingdirectory
Mar 25, 2010 4:32:11 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-216.55.168.27-8080
Mar 25, 2010 4:32:11 PM org.apache.coyote.tomcat5.MapperListener registerEngine
WARNING: Unknown default host: localhost
Mar 25, 2010 4:32:12 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8443
Mar 25, 2010 4:32:12 PM org.apache.coyote.tomcat5.MapperListener registerEngine
WARNING: Unknown default host: localhost
Mar 25, 2010 4:32:13 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /216.55.168.27:8009
Mar 25, 2010 4:32:13 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=9/258 config=/usr/share/tomcat5.0/conf/jk2.properties
Mar 25, 2010 4:32:13 PM org.apache.coyote.tomcat5.MapperListener registerEngine
WARNING: Unknown default host: localhost
Mar 25, 2010 4:32:13 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina2
Mar 25, 2010 4:32:13 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.28
Mar 25, 2010 4:32:13 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-66.226.76.184-8080
Mar 25, 2010 4:32:13 PM org.apache.coyote.http11.Http11Protocol start
SEVERE: Error starting endpoint
java.net.BindException: Address already in use:8443
at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:264)
at org.apache.tomcat.util.net.PoolTcpEndpoint.startEndpoint(PoolTcpEndpoint.java:281)
at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:171)
at org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.java:1527)
at org.apache.catalina.core.StandardService.start(StandardService.java:489)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
Mar 25, 2010 4:32:13 PM org.apache.catalina.startup.Catalina start
SEVERE: Catalina.start:
LifecycleException: Protocol handler start failed: java.net.BindException: Address already in use:8443
at org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.java:1529)
at org.apache.catalina.core.StandardService.start(StandardService.java:489)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
Mar 25, 2010 4:32:13 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 79290 ms
<!-- 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="Catalina1">
<!-- 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"
address="xx.xx.xx.xx" />
<!-- 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"
address="xx.xx.xx.xx" />
<!-- 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_log1." 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.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" 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:@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" 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="www.domain.com" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
<Alias>domain.com</Alias>
<!-- 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
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:
<%
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">
<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;"/>
<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"
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_log1." suffix=".txt"
timestamp="true"/>
<Context path="" docBase="datingdirectory"
debug="5" reloadable="true" crossContext="true">
<!-- maxActive: 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.
-->
<!-- maxIdle: Maximum number of idle dB connections to retain in pool.
Set to -1 for no limit. See also the DBCP documentation on this
and the minEvictableIdleTimeMillis configuration parameter.
-->
<!-- maxWait: 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.
-->
<!-- username and password: MySQL dB username and password for dB connections -->
<!-- driverClassName: Class name for the old mm.mysql JDBC driver is
org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
-->
<!-- url: 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.
-->
<Resource name="jdbc/datingdb"
auth="Container"
type="javax.sql.DataSource"/>
<!--
<Resource name="jdbc/datingdb" auth="Container" type="javax.sql.DataSource"
maxActive="100" maxIdle="30" maxWait="10000"
username="root" password="" driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost/datingdb"/>
-->
<ResourceParams name="jdbc/datingdb">
<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>
<!-- Remove abandoned connections -->
<parameter>
<name>removeAbandoned</name>
<value>true</value>
</parameter>
<parameter>
<name>removeAbandonedTimeout</name>
<value>60</value>
</parameter>
<parameter>
<name>logAbandoned</name>
<value>true</value>
</parameter>
<!-- MySQL dB username and password for dB connections -->
<parameter>
<name>username</name>
<value>usernamr</value>
</parameter>
<parameter>
<name>password</name>
<value>password</value>
</parameter>
<!-- Class name for mm.mysql JDBC driver -->
<parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.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/datingdb</value>
</parameter>
</ResourceParams>
</Context>
</Host>
<Host name="www.domain2.com" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
<Alias>domain2.com</Alias>
<!--
<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;"/>
<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"
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_log2." suffix=".txt"
timestamp="true"/>
<Context path="" docBase="tech"
debug="5" reloadable="true" crossContext="true">
<!-- maxActive: 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.
-->
<!-- maxIdle: Maximum number of idle dB connections to retain in pool.
Set to -1 for no limit. See also the DBCP documentation on this
and the minEvictableIdleTimeMillis configuration parameter.
-->
<!-- maxWait: 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.
-->
<!-- username and password: MySQL dB username and password for dB connections -->
<!-- driverClassName: Class name for the old mm.mysql JDBC driver is
org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
-->
<!-- url: 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.
-->
</Context>
</Host>
<Host name="www.domain3.com" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
<Alias>domain3.com</Alias>
<!--
<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;"/>
<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"
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_log2." suffix=".txt"
timestamp="true"/>
<Context path="" docBase="datingapp3"
debug="5" reloadable="true" crossContext="true">
<!-- maxActive: 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.
-->
<!-- maxIdle: Maximum number of idle dB connections to retain in pool.
Set to -1 for no limit. See also the DBCP documentation on this
and the minEvictableIdleTimeMillis configuration parameter.
-->
<!-- maxWait: 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.
-->
<!-- username and password: MySQL dB username and password for dB connections -->
<!-- driverClassName: Class name for the old mm.mysql JDBC driver is
org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
-->
<!-- url: 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.
-->
<Resource name="jdbc/datingdb"
auth="Container"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/datingdb">
<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>
<!-- Remove abandoned connections -->
<parameter>
<name>removeAbandoned</name>
<value>true</value>
</parameter>
<parameter>
<name>removeAbandonedTimeout</name>
<value>60</value>
</parameter>
<parameter>
<name>logAbandoned</name>
<value>true</value>
</parameter>
<!-- MySQL dB username and password for dB connections -->
<parameter>
<name>username</name>
<value>username</value>
</parameter>
<parameter>
<name>password</name>
<value>password</value>
</parameter>
<!-- Class name for mm.mysql JDBC driver -->
<parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.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/datingdb3</value>
</parameter>
</ResourceParams>
</Context>
</Host>
<Host name="www.domain4.com" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
<Alias>domain4.com</Alias>
<Alias>xx.xx.xx.xx</Alias>
<!--
<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;"/>
<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"
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_log2." suffix=".txt"
timestamp="true"/>
<Context path="" docBase="datingapp2"
debug="5" reloadable="true" crossContext="true">
<!-- maxActive: 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.
-->
<!-- maxIdle: Maximum number of idle dB connections to retain in pool.
Set to -1 for no limit. See also the DBCP documentation on this
and the minEvictableIdleTimeMillis configuration parameter.
-->
<!-- maxWait: 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.
-->
<!-- username and password: MySQL dB username and password for dB connections -->
<!-- driverClassName: Class name for the old mm.mysql JDBC driver is
org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
-->
<!-- url: 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.
-->
<Resource name="jdbc/datingdb"
auth="Container"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/datingdb">
<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>
<!-- Remove abandoned connections -->
<parameter>
<name>removeAbandoned</name>
<value>true</value>
</parameter>
<parameter>
<name>removeAbandonedTimeout</name>
<value>60</value>
</parameter>
<parameter>
<name>logAbandoned</name>
<value>true</value>
</parameter>
<!-- MySQL dB username and password for dB connections -->
<parameter>
<name>username</name>
<value>username</value>
</parameter>
<parameter>
<name>password</name>
<value>password</value>
</parameter>
<!-- Class name for mm.mysql JDBC driver -->
<parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.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/datingdb2</value>
</parameter>
</ResourceParams>
</Context>
</Host>
<Host name="www.domain5.com" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
<Alias>domain5.com</Alias>
<!--
<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;"/>
<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"
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_log2." suffix=".txt"
timestamp="true"/>
<Context path="" docBase="tech2"
debug="5" reloadable="true" crossContext="true">
<!-- maxActive: 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.
-->
<!-- maxIdle: Maximum number of idle dB connections to retain in pool.
Set to -1 for no limit. See also the DBCP documentation on this
and the minEvictableIdleTimeMillis configuration parameter.
-->
<!-- maxWait: 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.
-->
<!-- username and password: MySQL dB username and password for dB connections -->
<!-- driverClassName: Class name for the old mm.mysql JDBC driver is
org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
-->
<!-- url: 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.
-->
</Context>
</Host>
</Engine>
</Service>
<Service name="Catalina2">
<!-- 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"
address="xx.xx.xx.xx" />
<!-- 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"
address="xx.xx.xx.xx" />
<!-- 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="www.domain4.com" debug="0" jvmRoute="jvm1">
-->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Catalina" defaultHost="www.domain4.com" 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_log2." 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.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" 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:@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" 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.
-->
</Engine>
</Service>
</Server>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Why is tomcat taking so long to start?
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mon,
On 3/25/2010 8:30 PM, Mon Cab wrote:
> <Engine name="Catalina" defaultHost="localhost" debug="0">
Note that you never define the host "localhost" which is why you are
getting those warning messages in your log file.
> <Host name="www.domain.com" debug="0" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
> <Alias>domain.com</Alias>
> [...]
> </Host>
>
> <Host name="www.domain2.com" debug="0" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
> <Alias>domain2.com</Alias>
> [...]
> </Host>
>
> <Host name="www.domain4.com" debug="0" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
> <Alias>domain4.com</Alias>
> <Alias>xx.xx.xx.xx</Alias>
> [...]
> </Host>
>
> <Host name="www.domain5.com" debug="0" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
> <Alias>domain5.com</Alias>
> [...]
Why are you defining so many hosts and re-deploying the same webapps
over and over again? Why not simply make all domains aliases of each
other? You'll save startup time and memory, plus have fewer management
headaches.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkus48cACgkQ9CaO5/Lv0PCiyACfapvTMMCiNkC0wrkYOYnuc6qz
/88Aniouo3xV6PJzG+bl5HmGGtPQ0pPI
=xzS1
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Why is tomcat taking so long to start?
Posted by Juha Laiho <Ju...@iki.fi>.
On 26.3.2010 2:30, Mon Cab wrote:
> Tomcat is taking 3 mins to start up, while it used to start up in a matter of seconds.
> We have 2 containers set up with 7-9 hosts configured, each with its own docbase directory.
>
> Looking at the working directory, it seems that there is a directory for each host and for some
> unknown reason within that directory there are directories for each of the other hosts docbases
>
> ie.
>
> work
> |
> |-catalina
> -- domain1.com
> |
> |- docbase for domain1
> |- docbase for domain 2
> ...
> -- docbase for domain7
>
> -- domain2.com
> |
> |- docbase for domain1
> |- docbase for domain 2
> ...
> -- docbase for domain7
>
>
> Is this supposed to happen?
That's actually quite curious. Your configuration looks like you have
just one application running on each domain, but the log looks like
it is starting up all applications for all domains. That alone makes
it take quite some time. You might wish to check your deployment
practices.
A somewhat related thing is that the time seems to be consumed primarily
in the application startup phase. Once after you find and correct the
reason for this "all apps on all domains" issue, you might wish to
increase per-application logging to such a level that you can see
what is going on - unless just solving this primary problem is enough.
Of course, one way to find the solution would be to find "what changed"
at the time the response time increased from the old "seconds" to the
current.
--
..Juha
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Why is tomcat taking so long to start?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Mon Cab [mailto:futon33@yahoo.com]
> Subject: RE: Why is tomcat taking so long to start?
>
> While this may be an unsupported version of Tomcat, version support is
> not an issue for us here.
But it is for people who volunteer to support Tomcat - even the doc for that level is difficult to access.
> What are the other problems you alluded to?
Please upgrade to a supported version so we can discuss them.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Why is tomcat taking so long to start?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Steffen Heil [mailto:lists@steffen-heil.de]
> Subject: AW: Why is tomcat taking so long to start?
>
> > While this may be an unsupported version of Tomcat, version support
> > is not an issue for us here.
>
> Support is not an issue for you, still you are asking for support?
Good that someone else noticed that disconnect...
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
AW: Why is tomcat taking so long to start?
Posted by Steffen Heil <li...@steffen-heil.de>.
> While this may be an unsupported version of Tomcat, version support is not
an issue for us here.
Support is not an issue for you, still you are asking for support?
RE: Why is tomcat taking so long to start?
Posted by Mon Cab <fu...@yahoo.com>.
Charles
While this may be an unsupported version of Tomcat, version support is not an issue for us here. I am guessing that Tomcat 5.0 should not be having these issues, just because it is no longer supported.
What are the other problems you alluded to?
--- On Thu, 3/25/10, Caldarale, Charles R <Ch...@unisys.com> wrote:
> From: Caldarale, Charles R <Ch...@unisys.com>
> Subject: RE: Why is tomcat taking so long to start?
> To: "Tomcat Users List" <us...@tomcat.apache.org>
> Date: Thursday, March 25, 2010, 5:56 PM
> > From: Pid [mailto:pid@pidster.com]
> > Subject: Re: Why is tomcat taking so long to start?
> >
> > You have some errors there, you're trying to start
> multiple Connectors
> > on port 8443, so the second one fails.
>
> To say nothing of several other problems, the most glaring
> of which is using an unsupported version of Tomcat.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR
> OTHERWISE PROPRIETARY MATERIAL and is thus for use only by
> the intended recipient. If you received this in error,
> please contact the sender and delete the e-mail and its
> attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Why is tomcat taking so long to start?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Pid [mailto:pid@pidster.com]
> Subject: Re: Why is tomcat taking so long to start?
>
> You have some errors there, you're trying to start multiple Connectors
> on port 8443, so the second one fails.
To say nothing of several other problems, the most glaring of which is using an unsupported version of Tomcat.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Why is tomcat taking so long to start?
Posted by Pid <pi...@pidster.com>.
On 26/03/2010 00:30, Mon Cab wrote:
> Tomcat is taking 3 mins to start up, while it used to start up in a matter of seconds.
> We have 2 containers set up with 7-9 hosts configured, each with its own docbase directory.
>
> Looking at the working directory, it seems that there is a directory for each host and for some
> unknown reason within that directory there are directories for each of the other hosts docbases
>
> ie.
Nothing like removing the comments from your server.xml to make it
easier to read.
You have some errors there, you're trying to start multiple Connectors
on port 8443, so the second one fails.
p
> work
> |
> |-catalina
> -- domain1.com
> |
> |- docbase for domain1
> |- docbase for domain 2
> ...
> -- docbase for domain7
>
> -- domain2.com
> |
> |- docbase for domain1
> |- docbase for domain 2
> ...
> -- docbase for domain7
>
>
> Is this supposed to happen?
> I included the catalina log file below, and the server-conf file below that.
>
>
>
> Mar 25, 2010 4:30:53 PM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-216.55.168.27-8080
> Mar 25, 2010 4:30:54 PM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-8443
> Mar 25, 2010 4:30:54 PM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-66.226.76.184-8080
> Mar 25, 2010 4:30:54 PM org.apache.coyote.http11.Http11Protocol init
> SEVERE: Error initializing endpoint
> java.net.BindException: Address already in use:8443
> at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:264)
> at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:137)
> at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1429)
> at org.apache.catalina.core.StandardService.initialize(StandardService.java:609)
> at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:2384)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:507)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:528)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:250)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:424)
> Mar 25, 2010 4:30:54 PM org.apache.catalina.startup.Catalina load
> SEVERE: Catalina.start
> LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use:8443
> at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1431)
> at org.apache.catalina.core.StandardService.initialize(StandardService.java:609)
> at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:2384)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:507)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:528)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:250)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:424)
> Mar 25, 2010 4:30:54 PM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 4047 ms
> Mar 25, 2010 4:30:54 PM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina1
> Mar 25, 2010 4:30:54 PM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.0.28
> Mar 25, 2010 4:30:54 PM org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> log4j:INFO Using URL [file:/usr/share/tomcat5.0/common/classes/log4j.xml] for automatic log4j configuration of repository named [default].
> Mar 25, 2010 4:30:59 PM org.apache.catalina.core.StandardHost getDeployer
> INFO: Create Host deployer for direct deployment ( non-jmx )
> Mar 25, 2010 4:30:59 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp2 from URL file:/usr/share/tomcat5.0/webapps/datingapp2
> Mar 25, 2010 4:31:02 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp from URL file:/usr/share/tomcat5.0/webapps/datingapp
> Mar 25, 2010 4:31:03 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech2 from URL file:/usr/share/tomcat5.0/webapps/tech2
> Mar 25, 2010 4:31:04 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech from URL file:/usr/share/tomcat5.0/webapps/tech
> Mar 25, 2010 4:31:06 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech0 from URL file:/usr/share/tomcat5.0/webapps/tech0
> Mar 25, 2010 4:31:07 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /webdav from URL file:/usr/share/tomcat5.0/webapps/webdav
> Mar 25, 2010 4:31:07 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /basementbeat1 from URL file:/usr/share/tomcat5.0/webapps/basementbeat1
> Mar 25, 2010 4:31:08 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp3 from URL file:/usr/share/tomcat5.0/webapps/datingapp3
> Mar 25, 2010 4:31:11 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /basementbeat0 from URL file:/usr/share/tomcat5.0/webapps/basementbeat0
> Mar 25, 2010 4:31:13 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingdirectory from URL file:/usr/share/tomcat5.0/webapps/datingdirectory
> Mar 25, 2010 4:31:15 PM org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> Mar 25, 2010 4:31:16 PM org.apache.catalina.core.StandardHost getDeployer
> INFO: Create Host deployer for direct deployment ( non-jmx )
> Mar 25, 2010 4:31:16 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp2 from URL file:/usr/share/tomcat5.0/webapps/datingapp2
> Mar 25, 2010 4:31:19 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp from URL file:/usr/share/tomcat5.0/webapps/datingapp
> Mar 25, 2010 4:31:21 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech2 from URL file:/usr/share/tomcat5.0/webapps/tech2
> Mar 25, 2010 4:31:23 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech from URL file:/usr/share/tomcat5.0/webapps/tech
> Mar 25, 2010 4:31:25 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech0 from URL file:/usr/share/tomcat5.0/webapps/tech0
> Mar 25, 2010 4:31:27 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /webdav from URL file:/usr/share/tomcat5.0/webapps/webdav
> Mar 25, 2010 4:31:28 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /basementbeat1 from URL file:/usr/share/tomcat5.0/webapps/basementbeat1
> Mar 25, 2010 4:31:30 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp3 from URL file:/usr/share/tomcat5.0/webapps/datingapp3
> Mar 25, 2010 4:31:34 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /basementbeat0 from URL file:/usr/share/tomcat5.0/webapps/basementbeat0
> Mar 25, 2010 4:31:35 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingdirectory from URL file:/usr/share/tomcat5.0/webapps/datingdirectory
> Mar 25, 2010 4:31:36 PM org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> Mar 25, 2010 4:31:38 PM org.apache.catalina.core.StandardHost getDeployer
> INFO: Create Host deployer for direct deployment ( non-jmx )
> Mar 25, 2010 4:31:38 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp2 from URL file:/usr/share/tomcat5.0/webapps/datingapp2
> Mar 25, 2010 4:31:40 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp from URL file:/usr/share/tomcat5.0/webapps/datingapp
> Mar 25, 2010 4:31:40 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech2 from URL file:/usr/share/tomcat5.0/webapps/tech2
> Mar 25, 2010 4:31:41 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech from URL file:/usr/share/tomcat5.0/webapps/tech
> Mar 25, 2010 4:31:42 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech0 from URL file:/usr/share/tomcat5.0/webapps/tech0
> Mar 25, 2010 4:31:43 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /webdav from URL file:/usr/share/tomcat5.0/webapps/webdav
> Mar 25, 2010 4:31:43 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /basementbeat1 from URL file:/usr/share/tomcat5.0/webapps/basementbeat1
> Mar 25, 2010 4:31:44 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp3 from URL file:/usr/share/tomcat5.0/webapps/datingapp3
> Mar 25, 2010 4:31:46 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /basementbeat0 from URL file:/usr/share/tomcat5.0/webapps/basementbeat0
> Mar 25, 2010 4:31:46 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingdirectory from URL file:/usr/share/tomcat5.0/webapps/datingdirectory
> Mar 25, 2010 4:31:48 PM org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> Mar 25, 2010 4:31:49 PM org.apache.catalina.core.StandardHost getDeployer
> INFO: Create Host deployer for direct deployment ( non-jmx )
> Mar 25, 2010 4:31:49 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp2 from URL file:/usr/share/tomcat5.0/webapps/datingapp2
> Mar 25, 2010 4:31:51 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp from URL file:/usr/share/tomcat5.0/webapps/datingapp
> Mar 25, 2010 4:31:51 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech2 from URL file:/usr/share/tomcat5.0/webapps/tech2
> Mar 25, 2010 4:31:52 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech from URL file:/usr/share/tomcat5.0/webapps/tech
> Mar 25, 2010 4:31:53 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech0 from URL file:/usr/share/tomcat5.0/webapps/tech0
> Mar 25, 2010 4:31:54 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /webdav from URL file:/usr/share/tomcat5.0/webapps/webdav
> Mar 25, 2010 4:31:54 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /basementbeat1 from URL file:/usr/share/tomcat5.0/webapps/basementbeat1
> Mar 25, 2010 4:31:55 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp3 from URL file:/usr/share/tomcat5.0/webapps/datingapp3
> Mar 25, 2010 4:31:57 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /basementbeat0 from URL file:/usr/share/tomcat5.0/webapps/basementbeat0
> Mar 25, 2010 4:31:57 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingdirectory from URL file:/usr/share/tomcat5.0/webapps/datingdirectory
> Mar 25, 2010 4:31:59 PM org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> Mar 25, 2010 4:32:01 PM org.apache.catalina.core.StandardHost getDeployer
> INFO: Create Host deployer for direct deployment ( non-jmx )
> Mar 25, 2010 4:32:01 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp2 from URL file:/usr/share/tomcat5.0/webapps/datingapp2
> Mar 25, 2010 4:32:03 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp from URL file:/usr/share/tomcat5.0/webapps/datingapp
> Mar 25, 2010 4:32:03 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech2 from URL file:/usr/share/tomcat5.0/webapps/tech2
> Mar 25, 2010 4:32:04 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech from URL file:/usr/share/tomcat5.0/webapps/tech
> Mar 25, 2010 4:32:05 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /tech0 from URL file:/usr/share/tomcat5.0/webapps/tech0
> Mar 25, 2010 4:32:06 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /webdav from URL file:/usr/share/tomcat5.0/webapps/webdav
> Mar 25, 2010 4:32:06 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /basementbeat1 from URL file:/usr/share/tomcat5.0/webapps/basementbeat1
> Mar 25, 2010 4:32:07 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingapp3 from URL file:/usr/share/tomcat5.0/webapps/datingapp3
> Mar 25, 2010 4:32:09 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /basementbeat0 from URL file:/usr/share/tomcat5.0/webapps/basementbeat0
> Mar 25, 2010 4:32:10 PM org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /datingdirectory from URL file:/usr/share/tomcat5.0/webapps/datingdirectory
> Mar 25, 2010 4:32:11 PM org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on http-216.55.168.27-8080
> Mar 25, 2010 4:32:11 PM org.apache.coyote.tomcat5.MapperListener registerEngine
> WARNING: Unknown default host: localhost
> Mar 25, 2010 4:32:12 PM org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on http-8443
> Mar 25, 2010 4:32:12 PM org.apache.coyote.tomcat5.MapperListener registerEngine
> WARNING: Unknown default host: localhost
> Mar 25, 2010 4:32:13 PM org.apache.jk.common.ChannelSocket init
> INFO: JK2: ajp13 listening on /216.55.168.27:8009
> Mar 25, 2010 4:32:13 PM org.apache.jk.server.JkMain start
> INFO: Jk running ID=0 time=9/258 config=/usr/share/tomcat5.0/conf/jk2.properties
> Mar 25, 2010 4:32:13 PM org.apache.coyote.tomcat5.MapperListener registerEngine
> WARNING: Unknown default host: localhost
> Mar 25, 2010 4:32:13 PM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina2
> Mar 25, 2010 4:32:13 PM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.0.28
> Mar 25, 2010 4:32:13 PM org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on http-66.226.76.184-8080
> Mar 25, 2010 4:32:13 PM org.apache.coyote.http11.Http11Protocol start
> SEVERE: Error starting endpoint
> java.net.BindException: Address already in use:8443
> at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:264)
> at org.apache.tomcat.util.net.PoolTcpEndpoint.startEndpoint(PoolTcpEndpoint.java:281)
> at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:171)
> at org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.java:1527)
> at org.apache.catalina.core.StandardService.start(StandardService.java:489)
> at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
> Mar 25, 2010 4:32:13 PM org.apache.catalina.startup.Catalina start
> SEVERE: Catalina.start:
> LifecycleException: Protocol handler start failed: java.net.BindException: Address already in use:8443
> at org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.java:1529)
> at org.apache.catalina.core.StandardService.start(StandardService.java:489)
> at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
> Mar 25, 2010 4:32:13 PM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 79290 ms
>
>
>
>
> <!-- 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="Catalina1">
>
> <!-- 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"
> address="xx.xx.xx.xx" />
>
> <!-- 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"
> address="xx.xx.xx.xx" />
>
> <!-- 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_log1." 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.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" 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:@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" 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="www.domain.com" debug="0" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
> <Alias>domain.com</Alias>
>
> <!-- 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
>
> 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:
> <%
> 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">
>
> <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;"/>
>
> <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"
> 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_log1." suffix=".txt"
> timestamp="true"/>
>
>
> <Context path="" docBase="datingdirectory"
> debug="5" reloadable="true" crossContext="true">
>
> <!-- maxActive: 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.
> -->
>
> <!-- maxIdle: Maximum number of idle dB connections to retain in pool.
> Set to -1 for no limit. See also the DBCP documentation on this
> and the minEvictableIdleTimeMillis configuration parameter.
> -->
>
> <!-- maxWait: 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.
> -->
>
> <!-- username and password: MySQL dB username and password for dB connections -->
>
> <!-- driverClassName: Class name for the old mm.mysql JDBC driver is
> org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
> Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
> -->
>
> <!-- url: 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.
> -->
>
>
> <Resource name="jdbc/datingdb"
> auth="Container"
> type="javax.sql.DataSource"/>
>
> <!--
> <Resource name="jdbc/datingdb" auth="Container" type="javax.sql.DataSource"
> maxActive="100" maxIdle="30" maxWait="10000"
> username="root" password="" driverClassName="com.mysql.jdbc.Driver"
> url="jdbc:mysql://localhost/datingdb"/>
> -->
>
> <ResourceParams name="jdbc/datingdb">
>
> <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>
>
> <!-- Remove abandoned connections -->
>
> <parameter>
> <name>removeAbandoned</name>
> <value>true</value>
> </parameter>
>
> <parameter>
> <name>removeAbandonedTimeout</name>
> <value>60</value>
> </parameter>
>
> <parameter>
> <name>logAbandoned</name>
> <value>true</value>
> </parameter>
>
>
> <!-- MySQL dB username and password for dB connections -->
> <parameter>
> <name>username</name>
> <value>usernamr</value>
> </parameter>
> <parameter>
> <name>password</name>
> <value>password</value>
> </parameter>
>
>
>
> <!-- Class name for mm.mysql JDBC driver -->
> <parameter>
> <name>driverClassName</name>
> <value>com.mysql.jdbc.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/datingdb</value>
> </parameter>
> </ResourceParams>
>
> </Context>
>
> </Host>
>
>
> <Host name="www.domain2.com" debug="0" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
> <Alias>domain2.com</Alias>
>
> <!--
> <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;"/>
>
> <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"
> 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_log2." suffix=".txt"
> timestamp="true"/>
>
>
> <Context path="" docBase="tech"
> debug="5" reloadable="true" crossContext="true">
>
> <!-- maxActive: 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.
> -->
>
> <!-- maxIdle: Maximum number of idle dB connections to retain in pool.
> Set to -1 for no limit. See also the DBCP documentation on this
> and the minEvictableIdleTimeMillis configuration parameter.
> -->
>
> <!-- maxWait: 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.
> -->
>
> <!-- username and password: MySQL dB username and password for dB connections -->
>
> <!-- driverClassName: Class name for the old mm.mysql JDBC driver is
> org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
> Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
> -->
>
> <!-- url: 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.
> -->
>
>
> </Context>
>
>
> </Host>
>
>
>
>
>
> <Host name="www.domain3.com" debug="0" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
> <Alias>domain3.com</Alias>
>
> <!--
> <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;"/>
>
> <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"
> 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_log2." suffix=".txt"
> timestamp="true"/>
>
>
> <Context path="" docBase="datingapp3"
> debug="5" reloadable="true" crossContext="true">
>
> <!-- maxActive: 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.
> -->
>
> <!-- maxIdle: Maximum number of idle dB connections to retain in pool.
> Set to -1 for no limit. See also the DBCP documentation on this
> and the minEvictableIdleTimeMillis configuration parameter.
> -->
>
> <!-- maxWait: 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.
> -->
>
> <!-- username and password: MySQL dB username and password for dB connections -->
>
> <!-- driverClassName: Class name for the old mm.mysql JDBC driver is
> org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
> Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
> -->
>
> <!-- url: 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.
> -->
>
>
> <Resource name="jdbc/datingdb"
> auth="Container"
> type="javax.sql.DataSource"/>
>
>
> <ResourceParams name="jdbc/datingdb">
>
> <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>
>
> <!-- Remove abandoned connections -->
>
> <parameter>
> <name>removeAbandoned</name>
> <value>true</value>
> </parameter>
>
> <parameter>
> <name>removeAbandonedTimeout</name>
> <value>60</value>
> </parameter>
>
> <parameter>
> <name>logAbandoned</name>
> <value>true</value>
> </parameter>
>
>
> <!-- MySQL dB username and password for dB connections -->
>
> <parameter>
> <name>username</name>
> <value>username</value>
> </parameter>
> <parameter>
> <name>password</name>
> <value>password</value>
> </parameter>
>
> <!-- Class name for mm.mysql JDBC driver -->
> <parameter>
> <name>driverClassName</name>
> <value>com.mysql.jdbc.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/datingdb3</value>
> </parameter>
> </ResourceParams>
>
> </Context>
>
>
> </Host>
>
>
> <Host name="www.domain4.com" debug="0" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
> <Alias>domain4.com</Alias>
> <Alias>xx.xx.xx.xx</Alias>
>
> <!--
> <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;"/>
>
> <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"
> 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_log2." suffix=".txt"
> timestamp="true"/>
>
>
> <Context path="" docBase="datingapp2"
> debug="5" reloadable="true" crossContext="true">
>
> <!-- maxActive: 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.
> -->
>
> <!-- maxIdle: Maximum number of idle dB connections to retain in pool.
> Set to -1 for no limit. See also the DBCP documentation on this
> and the minEvictableIdleTimeMillis configuration parameter.
> -->
>
> <!-- maxWait: 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.
> -->
>
> <!-- username and password: MySQL dB username and password for dB connections -->
>
> <!-- driverClassName: Class name for the old mm.mysql JDBC driver is
> org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
> Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
> -->
>
> <!-- url: 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.
> -->
>
>
> <Resource name="jdbc/datingdb"
> auth="Container"
> type="javax.sql.DataSource"/>
>
>
> <ResourceParams name="jdbc/datingdb">
>
> <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>
>
> <!-- Remove abandoned connections -->
>
> <parameter>
> <name>removeAbandoned</name>
> <value>true</value>
> </parameter>
>
> <parameter>
> <name>removeAbandonedTimeout</name>
> <value>60</value>
> </parameter>
>
> <parameter>
> <name>logAbandoned</name>
> <value>true</value>
> </parameter>
>
>
> <!-- MySQL dB username and password for dB connections -->
> <parameter>
> <name>username</name>
> <value>username</value>
> </parameter>
> <parameter>
> <name>password</name>
> <value>password</value>
> </parameter>
>
> <!-- Class name for mm.mysql JDBC driver -->
> <parameter>
> <name>driverClassName</name>
> <value>com.mysql.jdbc.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/datingdb2</value>
> </parameter>
> </ResourceParams>
>
> </Context>
>
> </Host>
>
>
> <Host name="www.domain5.com" debug="0" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
> <Alias>domain5.com</Alias>
>
> <!--
> <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;"/>
>
> <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"
> 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_log2." suffix=".txt"
> timestamp="true"/>
>
>
> <Context path="" docBase="tech2"
> debug="5" reloadable="true" crossContext="true">
>
> <!-- maxActive: 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.
> -->
>
> <!-- maxIdle: Maximum number of idle dB connections to retain in pool.
> Set to -1 for no limit. See also the DBCP documentation on this
> and the minEvictableIdleTimeMillis configuration parameter.
> -->
>
> <!-- maxWait: 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.
> -->
>
> <!-- username and password: MySQL dB username and password for dB connections -->
>
> <!-- driverClassName: Class name for the old mm.mysql JDBC driver is
> org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
> Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
> -->
>
> <!-- url: 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.
> -->
>
>
> </Context>
>
>
> </Host>
>
>
>
>
>
> </Engine>
>
> </Service>
>
> <Service name="Catalina2">
>
> <!-- 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"
> address="xx.xx.xx.xx" />
>
> <!-- 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"
> address="xx.xx.xx.xx" />
>
> <!-- 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="www.domain4.com" debug="0" jvmRoute="jvm1">
> -->
>
> <!-- Define the top level container in our container hierarchy -->
> <Engine name="Catalina" defaultHost="www.domain4.com" 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_log2." 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.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" 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:@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" 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.
> -->
>
>
> </Engine>
>
> </Service>
> </Server>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org