`

apache 2.X+tomcat 6.X/7.X集群配置

 
阅读更多

httpd-2.2.22-win32-x86-no_ssl.msi

tomcat-connectors-1.2.35-windows-i386-httpd-2.2.x.zip

tomcat 6 和tomcat7 都行  tomcat8 没有测试。

 

安装就不演示了,直接配置:

1.首先将下载的tomcat-connectors-1.2.35-windows-i386-httpd-2.2.x.zip解压复制里面的

mod_jk.so 复制到Apache安装目录的modules目录下

 

2.修改:

D:\Program Files\Apache Software Foundation\Apache2.2\conf\httpd.conf

 

最后一行加入:

include "D:\Program Files\Apache Software Foundation\Apache2.2\conf\mod_jk.conf"

访问系统路径

Alias /q2c "D:/q2c/q2c"

<Directory "D:/q2c/q2c">

     Options Indexes MultiViews

     AllowOverride None

     Order allow,deny

     Allow from all

</Directory>

注意:D:/q2c/q2c 红色的q2c为项目根目录,即我把项目放在了D盘q2c的文件夹下面

 

 

3.

 

创建:D:\Program Files\Apache Software Foundation\Apache2.2\conf\mod_jk.conf

 

 内容

 

LoadModule jk_module modules/mod_jk.so

 

JkWorkersFile conf/workers.properties

 

JkMount /* controller

 

#静态文件都例外,交给apache来处理 

 

JkUnMount /*.gif controller

 

JkUnMount /*.jpg controller

 

JkUnMount /*.png controller

 

JkUnMount /*.css controller

 

JkUnMount /*.js controller

 

JkUnMount /*.htm controller

 

JkUnMount /*.html controller

 

JkUnMount /*.xml controller

 

JkUnMount /*.db controller

 

JkUnMount /*.ico controller

 

JkUnMount /*.bmp controller

 

JkUnMount /*.swf controller

 

JkUnMount /*.doc controller

 

JkUnMount /*.ppt controller

 

JkUnMount /*.xls controller

 

JkUnMount /*.docx controller

 

JkUnMount /*.pptx controller

 

JkUnMount /*.xlsx controller

 

JkUnMount /*.pdf controller

 

JkUnMount /*.txt controller

 

 

 

 

 

4.新建:

D:\Program Files\Apache Software Foundation\Apache2.2\conf\workers.properties

内容

#server

worker.list = controller

#========tomcat1========

worker.tomcat1.port=8009

worker.tomcat1.host=172.168.20.4

worker.tomcat1.type=ajp13

worker.tomcat1.lbfactor = 1

#========tomcat2========

worker.tomcat2.port=8009

worker.tomcat2.host=172.168.20.5

worker.tomcat2.type=ajp13

worker.tomcat2.lbfactor = 1

#========tomcat3========

worker.tomcat3.port=8009

worker.tomcat3.host=172.168.20.6

worker.tomcat3.type=ajp13

worker.tomcat3.lbfactor = 1

#========controller,负载均衡控制器========

worker.controller.type=lb

worker.controller.balanced_workers=tomcat1,tomcat2,tomcat3

worker.controller.sticky_session=1

worker.controller.sticky_session_force=0

 

5.配置每个tomcatserver.xml

<?xml version='1.0' encoding='utf-8'?>
<!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
-->
<!-- Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
 -->
<Server port="8005" shutdown="SHUTDOWN">

  <!--APR library loader. Documentation at /docs/apr.html -->
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
  <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
  <Listener className="org.apache.catalina.core.JasperListener" />
  <!-- Prevent memory leaks due to use of particular java/javax APIs-->
  <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
  <!-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html -->
  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />

  <!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  -->
  <GlobalNamingResources>
    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    -->
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" />
  </GlobalNamingResources>

  <!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note:  A "Service" is not itself a "Container", 
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   -->
  <Service name="Catalina">
  
    <!--The connectors can use a shared executor, you can define one or more named thread pools-->
    <!--
    <Executor name="tomcatThreadPool" namePrefix="catalina-exec-" 
        maxThreads="150" minSpareThreads="4"/>
    -->
    
    
    <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8081
    -->
    <Connector port="8080" protocol="HTTP/1.1" 
               connectionTimeout="20000" 
               redirectPort="8443" />
    <!-- A "Connector" using the shared thread pool-->
    <!--
    <Connector executor="tomcatThreadPool"
               port="8081" protocol="HTTP/1.1" 
               connectionTimeout="20000" 
               redirectPort="8443" />
    -->           
    <!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the JSSE configuration, when using APR, the 
         connector should be using the OpenSSL style configuration
         described in the APR documentation -->
    <!--
    <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
               maxThreads="150" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <span style="color: #ff0000;"><Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />

</span>
    <!-- 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).
         Documentation at /docs/config/engine.html -->

    <!-- You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">         
    --> 
    <span style="color: #ff0000;"><Engine name="Catalina" defaultHost="localhost" jvmRoute="tomcat1">
</span>
      <!--For clustering, please take a look at documentation at:
          /docs/cluster-howto.html  (simple how to)
          /docs/config/cluster.html (reference documentation) -->
      
      <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
      

      <!-- The request dumper valve dumps useful debugging information about
           the request and response data received and sent by Tomcat.
           Documentation at: /docs/config/valve.html -->
      <!--
      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
      -->

      <!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  -->
      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase"/>

      <!-- Define the default virtual host
           Note: XML Schema validation will not work with Xerces 2.2.
       -->
      <span style="color: #ff0000;"><Host name="localhost"  appBase="d:/q2c"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false">
</span>
        <!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
        -->

        <!-- Access log processes all example.
             Documentation at: /docs/config/valve.html -->
        <!--
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"  
               prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/>
        -->

      </Host>
    </Engine>
  </Service>
</Server>

 修改红色地方。注意与workers.properties文件里面的配置一致。

ok了。放入自己的项目试一下吧。

说明一点apache server下的项目目录放静态文件

如果你的项目是war包,直接复制到tomcat指定的工程目录就行了。

分享到:
评论

相关推荐

    Apache2.2.x+Tomcat6.x+jk2.x做集群配置

    Apache2.2.x + Tomcat6.x + jk2.x 集群配置教程 在互联网服务中,为了提供高可用性和负载均衡,通常会采用集群技术。Apache HTTP Server(通常简称为Apache)与Tomcat的结合是常见的Web服务器与应用服务器组合。...

    Apache2.2.25 + Tomcat6.0.45 + mod_jk + 测试页面 + 集群

    本资源包含了文章Apache2.2.x + Tomcat6.x + JK 集群配置,http://blog.csdn.net/qq396229783/article/details/74295797里面所用到的软件配置

    apache+tomcat集群配置

    Apache + Tomcat 集群配置 Apache + Tomcat 集群配置是指将 Apache 服务器与 Tomcat 服务器集成,以提高服务器的性能和可扩展性。本文将详细介绍如何配置 Apache + Tomcat 集群,包括安装 Apache 和 Tomcat 服务器...

    Apache2.4+tomcat7集群

    Apache2.4与Tomcat7集群的搭建是一个常见的高可用性和负载均衡的解决方案,尤其适用于大型Web应用程序。这个集群配置可以提升网站的性能,通过在多个服务器之间分发请求,提高系统的可扩展性和稳定性。 首先,...

    Apache动态域名+JK+Tomcat添加Tomcat系统服务 集群

    这一步骤是整个集群配置的基础。 ##### 1. 安装Apache2.2.4 **步骤一:下载Apache** 首先需要从Apache官方网站下载适合Windows平台的安装包。下载地址为:[http://archive.apache.org/dist/httpd/binaries/win32/...

    apache+tomcat集群.doc

    ### Apache + Tomcat 集群配置详解 #### 背景介绍 随着互联网应用规模的不断增大,单台服务器已经难以满足日益增长的服务需求。为了提高系统的可用性与性能,构建一个高可用且高性能的应用架构变得尤为重要。在这种...

    apache-tomcat-9.0.65-windows-x64.zip

    在本例中,我们讨论的是Apache Tomcat的第9.0.65版本,专为Windows x64操作系统设计。这个压缩包包含了运行和管理Java Web应用程序所需的所有组件。 首先,让我们深入了解Tomcat的架构和组成部分: 1. **Catalina*...

    Nginx+KeepAlived+Tomcat负载架构

    ./jdk-6u45-linux-x64-rpm.bin export JAVA_HOME=/usr/java/jdk_45 export CLASSPATH=.:$JAVA_HOME/jre/lib/rt.jar:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar export PATH=$PATH:$JAVA_HOME/bin source ...

    apache-tomcat-9.0.65

    2. **Java兼容性**:Tomcat 9.x系列支持Java EE 8标准,这意味着它可以运行使用Java Servlet 4.0、JSP 2.3和EL 3.0等技术编写的Web应用。 3. **目录结构**:解压后,你会看到如`bin`、`conf`、`lib`、`webapps`、`...

    mod_jk(包含apache2.4.x和apache2.2.x的两种版本)

    **Apache mod_jk模块详解与Tomcat集群配置** Apache mod_jk是Apache HTTP服务器的一个模块,主要用于连接Apache和Tomcat,实现两者之间的通信。在Java应用服务器领域,Tomcat广泛用作Servlet和JSP容器,而Apache则...

    apache-tomcat-8.5.92.tar.gz

    Apache Tomcat 8.5.x 系列是Tomcat的长期支持版本,它提供了对Java EE 7规范的全面支持。8.5.92是该系列的一个更新,包含了一些bug修复、安全改进和性能优化。Tomcat的设计目标是轻量级、高效且易于管理,使其成为...

    Apache+多个Tomcat 服务器集群配置

    将以下Module的注释去掉,这里并没有使用mod_jk.so进行apache和tomcat的链接,从2.X以后apache自身已集成了mod_jk.so的功能。只需简单的把下面几行去掉注释,就相当于以前用mod_jk.so比较繁琐的配置了。这里主要采用...

    官方原版apache-tomcat-9.0.34.tar.gz

    9. **集群与负载均衡**:Tomcat支持集群配置,通过复制应用状态在多个实例间提供高可用性和容错性。配合负载均衡器,可以将请求分发到多个Tomcat实例,提升系统处理能力。 10. **最新特性**:Tomcat 9.0.34版本可能...

    apache-tomcat-8.5.78.tar.gz

    - Tomcat支持集群配置,可以创建多个实例以实现负载均衡和故障转移。 - 需要配置共享的session存储机制,如基于数据库或分布式缓存。 9. **性能调优**: - 调整JVM参数,如堆大小(-Xms, -Xmx)、新生代大小(-XX:...

    apache+tomcat集群的基本配置(简明)

    ### Apache+Tomcat集群...**步骤2:取消注释集群配置** 取消`&lt;Cluster&gt;`标签的注释,启用集群功能。 ##### 3.3 测试集群 在每个Tomcat的`webapps`目录下新建`test`目录,并创建`test2.jsp`文件,代码如下: ```jsp ...

    apache+tomcat分布式部署

    每个Tomcat实例都有自己的AJP端口(`worker.tomcatX.port`),主机名(`worker.tomcatX.host`),类型(`worker.tomcatX.type`)和负载权重(`worker.tomcatX.lbfactor`)。`worker.controller.balanced_workers`指定了哪些...

    apache-tomcat-9.0.60.tar.gz

    7. **版本更新**:Apache Tomcat 9.0.x 系列引入了Java EE 8的支持,提供了最新的特性和改进,如HTTP/2支持,增强了安全性并修复了已知问题。 8. **跨平台性**:尽管Tomcat在Linux和Unix系统上运行最常见,但也可以...

Global site tag (gtag.js) - Google Analytics