Windows系统下配置Nginx1.1.12+tomcat5实现负载均衡-Nginx-中存储网

2013-12-29 10:31:01

来源
kejihao

Nginx

本文介绍Windows系统下配置Nginx1.1.12+tomcat5实现负载均衡，希望对于初学Nginx服务器相关的朋友有帮助，更多Nginx安装、配置、报错处理等资源请本站内搜索。。

发这个帖子可能是在班门弄斧，但还是希望跟大家分享一下。

准备的环境

nginx-1.1.12

tomcat5

windows7

Nginx配置

主要是修改conf/nginx.conf文件

#用户组表示哪个用户组下的用户启动。格式为：user username groupname; username为用户名,groupname为组名

#user nobody;

#工作进成数(通常写CPU数量或者2倍的CPU数量)

worker_processes 2;

#error_log logs/error.log;

#error_log logs/error.log notice;

error_log logs/error.log info;

#进程号保存文件

pid logs/nginx.pid;

#指定最大的文件描述符值,可以通过这个进程打开 (默认没有该设置)

#worker_rlimit_nofile 1024;

events {

#连接数，默认1024

worker_connections 1024;

}

http {

#文件扩展名与文件类型映射表

include mime.types;

default_type application/octet-stream;

#日志格式

log_format main '$remote_addr - $remote_user [$time_local] "$request" '

'$status $body_bytes_sent "$http_referer" '

'"$http_user_agent" "$http_x_forwarded_for"';

#access_log logs/access.log main;

sendfile on;

tcp_nopush on;

tcp_nodelay on;

client_header_timeout 3m;

client_body_timeout 3m;

send_timeout 3m;

client_header_buffer_size 1k;

large_client_header_buffers 4 4k;

#keepalive_timeout 0;

#长连接超时时间

keepalive_timeout 300;

#数据压缩流，可提高效率

include gzip.conf;

#设定负载均衡的服务器列表

upstream myserver {

#weigth参数表示权值，权值越高被分配到的几率越大

#本机上的Squid开启3128端口

server 127.0.0.1:8888 weight=1;

server 127.0.0.1:8887 weight=1;

}

server {

listen 8088;

server_name 127.0.0.1;

#字符集编码

charset utf-8;

#设定本虚拟主机的访问日志

access_log logs/host.access.log main;

#默认打开文件

location / {

proxy_connect_timeout 3;

proxy_send_timeout 30;

proxy_read_timeout 30;

proxy_pass http://myserver;

}

在conf目录下建立文件

gzip.conf文件

内容如下：

gzip on;

gzip_min_length 1000;

gzip_types text/plain text/css application/x-javascript;

Tomcat配置

主要是server.xml文件

<!-- 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.

-->

<!-- Comment these entries out to disable JMX MBeans support used for the

administration web application -->

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

UserDatabaseRealm to authenticate users -->

<!-- <Resource name="jdbc/CSCJNDI" auth="Container"

type="javax.sql.DataSource" driverClassName="oracle.jdbc.driver.OracleDriver"

url="jdbc:oracle:thin:@10.1.20.55:1521:orainst"

username="cscadmin" password="csc" maxActive="20" maxIdle="10"

maxWait="-1"/> -->

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

type="org.apache.catalina.UserDatabase"

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

factory="org.apache.catalina.users.MemoryUserDatabaseFactory"

pathname="conf/tomcat-users.xml" />

</GlobalNamingResources>

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

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

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

but this is not required.

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

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

-->

<!-- 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%binkeytool -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.

-->

<Connector port="8887" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

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

debug="0" connectionTimeout="20000"

disableUploadTimeout="true" URIEncoding="utf-8"/>

<!--

<Connector port="8085" maxHttpHeaderSize="8192"

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

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

connectionTimeout="20000" URIEncoding="UTF-8" useURIValidationHack="false" disableUploadTimeout="true"/>

-->

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

to 0 -->

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

compression="on"

compressionMinSize="2048"

noCompressionUserAgents="gozilla, traviata"

compressableMimeType="text/html,text/xml"

-->

<!--

<Connector port="8443" maxHttpHeaderSize="8192"

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

enableLookups="false" disableUploadTimeout="true"

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

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

-->

<Connector port="9009"

enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />

<!--

<Connector port="8082"

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

enableLookups="false" acceptCount="100" connectionTimeout="20000"

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

-->

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

every request. The Engine implementation for Tomcat stand alone

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

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

<!-- You should set jvmRoute to support load-balancing via AJP ie :

-->

<!-- 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. -->

<!--

-->

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

resources under the key "UserDatabase". Any edits

that are performed against this UserDatabase are immediately

available for use by the Realm. -->

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

resourceName="UserDatabase"/>

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

need to go back quickly -->

<!--

-->

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

stored in a database and accessed via JDBC -->

<!--

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

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

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

connectionName="test" connectionPassword="test"

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

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

-->

<!--

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

driverName="oracle.jdbc.driver.OracleDriver"

connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"

connectionName="scott" connectionPassword="tiger"

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

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

-->

<!--

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

driverName="sun.jdbc.odbc.JdbcOdbcDriver"

connectionURL="jdbc:odbc:CATALINA"

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

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

-->

<!-- Define the default virtual host

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

-->

<Host name="localhost" appBase="D:workwork_bztestWebRoot"

unpackWARs="true" autoDeploy="true"

xmlValidation="false" xmlNamespaceAware="false">

<!-- Defines a cluster for this node,

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

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

that need to be clustered and remove the other ones.

A cluster has the following parameters:

className = the fully qualified name of the cluster class

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

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

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

mcastBindAddr = bind the multicast socket to a specific address

mcastTTL = the multicast TTL if you want to limit your broadcast

mcastSoTimeout = the multicast readtimeout

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

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

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

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

in case of multiple ethernet cards.

auto means that address becomes

InetAddress.getLocalHost().getHostAddress()

tcpListenPort = the tcp listen port

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

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

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

expireSessionsOnShutdown = true means that

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

false means to replicate the session after each request.

false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)

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

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

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

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

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

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

nodes have received the information.

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

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

and then return to the client.

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

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

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

large network delay.

-->

<!--

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

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

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

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

2. a session exists (has been created)

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

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

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

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

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

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

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

ending with .gif and .js are intercepted.

The deployer element can be used to deploy apps cluster wide.

Currently the deployment only deploys/undeploys to working members in the cluster

so no WARs are copied upons startup of a broken node.

The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"

When a new war file is added the war gets deployed to the local instance,

and then deployed to the other instances in the cluster.

When a war file is deleted from the watchDir the war is undeployed locally

and cluster wide

-->

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

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

expireSessionsOnShutdown="false"

useDirtyFlag="true"

notifyListenersOnReplication="true">

<Membership

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

mcastAddr="228.0.0.4"

mcastPort="45564"

mcastFrequency="500"

mcastDropTime="3000"/>

<Receiver

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

tcpListenAddress="auto"

tcpListenPort="4002"

tcpSelectorTimeout="5000"

tcpThreadCount="6"/>

<Sender

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

replicationMode="pooled"

ackTimeout="15000"/>

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

filter=".*.gif;.*.js;.*.jpg;.*.png;.*.htm;.*.html;.*.css;.*.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. -->

<!--

-->

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

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

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

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

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

-->

<!--

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

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

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

-->

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

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

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

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

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

This access log implementation is optimized for maximum performance,

but is hardcoded to support only the "common" and "combined" patterns.

-->

<!--

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

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

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

-->

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

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

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

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

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

This access log implementation is optimized for maximum performance,

but is hardcoded to support only the "common" and "combined" patterns.

This valve use NIO direct Byte Buffer to asynchornously store the

log.

-->

<!--

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

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

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

-->

</Host>

</Engine>

</Service>

</Server>

经过实验是可以实现负载均衡和复制session的。

声明： 此文观点不代表本站立场；转载须要保留原文链接；版权疑问请联系我们。

Windows系统下配置Nginx1.1.12+tomcat5实现负载均衡

Apache和nginx配置不缓存文件

nginx环境中安装配置awstats统计

centos 6.1安装配置nginx和php

CentOS编译方式安装Nginx服务器

Nginx服务器负载均衡配置

科技要闻

ARM PC对x86移动平台构成严重威胁

美国预计到 2032 年半导体制造能力将增加两倍，成为世界上增长最快的国家

全球室外供暖市场将从 2024 年的 13.3 亿美元扩大到 2032 年的 21.5 亿美元

戴尔多云数据保护和人工智能技术进步，以应对日益增长的网络攻击

佰维存储发布工规级宽温LPDDR4X嵌入式存储芯片

Windows系统下配置Nginx1.1.12+tomcat5实现负载均衡

相关推荐

科技要闻