


How to configure Nginx load balancing multiple tomcats under Linux
One: Enter the conf directory under the nginx directory
This is my nginx installation directory:
[root@aliserver ~]# cd /usr/local/nginx/conf
Two: Edit nginx.conf
[root@aliserver conf]# vi nginx.conf
Three: Configure server group
1: Add upstream configuration between http{} nodes. (Be careful not to write localhost, otherwise the access speed will be very slow)
upstream nginxdemo { server 127.0.0.1:8081; #服务器地址1 server 127.0.0.1:8082; #服务器地址2 server 127.0.0.1:8082; #服务器地址3 server 127.0.0.1:8083; #服务器地址4 }
2: Modify the port number that nginx listens to 80
nginx default port is 80, I have not changed it here yet. Remain unchanged
server { listen 80; #默认是80,也可更改为其他的,当然已被占用的端口号不能写。 ...... }
3: Use proxy_pass to configure the reverse proxy address
In location\{}, "http://" cannot be missing here, and the following address must be the same as In the first step, the name defined by upstream should be consistent (that is, the name of nginxdemo is customized and needs to be consistent in both places)
location / { root html; index index.html index.htm; proxy_pass http://nginxdemo; #配置方向代理地址 }
After the configuration is completed, as shown in the figure:
Four: Start nginx
My installation path of nginx is /usr/local/nginx
So my startup command Yes:
[root@aliserver ~]# /usr/local/nginx/sbin/nginx
Because nginx has been started before installation, and now it reports an error that the port number is occupied when it is started again
At this time we use Command to check the occupancy of each port number
[root@aliserver ~]# netstat -ntpl
We see that nginx is occupied by the pid 9097, use kill -9 to kill it
[root@aliserver ~]# kill -9 9097
Start it again nginx
[root@aliserver ~]# /usr/local/nginx/sbin/nginx
has no response, that’s right. At this time, enter your server address
in the browser, indicating that nginx started successfully. As for whether the configuration is correct and whether the load can be balanced, let's start verifying it now. . .
5: Verification
We all know that when nginx load balancing, all client requests go through nginx, then nginx can decide who to forward these requests to. If Server A has more sufficient resources (more CPUs, larger memory, etc.), and Server B does not have as strong a processing capability as Server A. Then nginx will forward more requests to Server A and fewer requests to Server B, so that This achieves load balancing, and even if one of the servers is down, users can still access the website normally.
Before verification, you need to make some preparations.
1: Prepare a simpler jsp, such as:
I have 4 tomcats installed on a server, so I prepared The four index.jsp files
are
<title>tomcat8080<title> <h1 id="hellow-nbsp-tomcat">hellow tomcat_8080</h1> <title>tomcat8081<title> <h1 id="hellow-nbsp-tomcat">hellow tomcat_8081</h1> <title>tomcat8082<title> <h1 id="hellow-nbsp-tomcat">hellow tomcat_8082</h1> <title>tomcat8083<title> <h1 id="hellow-nbsp-tomcat">hellow tomcat_8083</h1>
. What needs to be noted here is: the name of the jsp file must be index.jsp, because the picture of tomcat starting successfully is as shown in the figure:
Reading is webapps/root/index.jsp in the tomcat installation directory
My address is:/usr/java/tomcat/tomcat_8080/ webapps/root
Overwrite each tomcat's default index.jsp file with the four previously prepared index.jsp files.
Start each tomcat
[root@aliserver bin]# ./startup.sh
At this time, we enter xxx.xxx.xx.xx:8080 in the browser. You will find that the kitten no longer appears, but. . . . . .
The above is the detailed content of How to configure Nginx load balancing multiple tomcats under Linux. For more information, please follow other related articles on the PHP Chinese website!

NGINX is more suitable for handling high concurrent connections, while Apache is more suitable for scenarios where complex configurations and module extensions are required. 1.NGINX is known for its high performance and low resource consumption, and is suitable for high concurrency. 2.Apache is known for its stability and rich module extensions, which are suitable for complex configuration needs.

NGINXUnit improves application flexibility and performance with its dynamic configuration and high-performance architecture. 1. Dynamic configuration allows the application configuration to be adjusted without restarting the server. 2. High performance is reflected in event-driven and non-blocking architectures and multi-process models, and can efficiently handle concurrent connections and utilize multi-core CPUs.

NGINX and Apache are both powerful web servers, each with unique advantages and disadvantages in terms of performance, scalability and efficiency. 1) NGINX performs well when handling static content and reverse proxying, suitable for high concurrency scenarios. 2) Apache performs better when processing dynamic content and is suitable for projects that require rich module support. The selection of a server should be decided based on project requirements and scenarios.

NGINX is suitable for handling high concurrent requests, while Apache is suitable for scenarios where complex configurations and functional extensions are required. 1.NGINX adopts an event-driven, non-blocking architecture, and is suitable for high concurrency environments. 2. Apache adopts process or thread model to provide a rich module ecosystem that is suitable for complex configuration needs.

NGINX can be used to improve website performance, security, and scalability. 1) As a reverse proxy and load balancer, NGINX can optimize back-end services and share traffic. 2) Through event-driven and asynchronous architecture, NGINX efficiently handles high concurrent connections. 3) Configuration files allow flexible definition of rules, such as static file service and load balancing. 4) Optimization suggestions include enabling Gzip compression, using cache and tuning the worker process.

NGINXUnit supports multiple programming languages and is implemented through modular design. 1. Loading language module: Load the corresponding module according to the configuration file. 2. Application startup: Execute application code when the calling language runs. 3. Request processing: forward the request to the application instance. 4. Response return: Return the processed response to the client.

NGINX and Apache have their own advantages and disadvantages and are suitable for different scenarios. 1.NGINX is suitable for high concurrency and low resource consumption scenarios. 2. Apache is suitable for scenarios where complex configurations and rich modules are required. By comparing their core features, performance differences, and best practices, you can help you choose the server software that best suits your needs.

Question: How to start Nginx? Answer: Install Nginx Startup Nginx Verification Nginx Is Nginx Started Explore other startup options Automatically start Nginx


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

SublimeText3 English version
Recommended: Win version, supports code prompts!

SublimeText3 Chinese version
Chinese version, very easy to use

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software