nginx集群tomcat 实现负载均衡（windows）

最新推荐文章于 2024-07-21 12:45:55 发布
最新推荐文章于 2024-07-21 12:45:55 发布
阅读量522 收藏 1
点赞数
分类专栏： tomcat+nginx
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/sky274548769/article/details/81981765
版权

1、生产环境下tomcat配置
tomcat是一个java服务器，主要用于管理和维护我们的servlet、jsp组件。
下载免安装版本的tomcat，直接解压出来，前提是jdk已经安装完成，直接解压就可以使用，为了后面集群，我们取名tomcat1，复制一个，取名tomcat2
这里写图片描述

1、修改端口：在生产环境中，一般我们的项目访问是不需要端口的，原因是浏览器默认使用80端口，所以如果一个tomcat来运行整个项目，那我们可以吧tomcat配置成80端口，

 <Connector port="80" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />

同时修改我们默认访问项目的路径：吧tomcat默认的项目路径由webapps改到我们制定的目录

 <Host name="localhost"  appBase="D:/server/project"
            unpackWARs="true" autoDeploy="true">
        <Context path="" docBase="D:/server/project" reloadable="true"/> 
        <!-- 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
             Note: The pattern used is equivalent to using pattern="common" -->
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log." suffix=".txt"
               pattern="%h %l %u %t &quot;%r&quot; %s %b" />

        </Host>

2、配置最大连接数和最大并发数量

  <Connector port="80" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" acceptCount="500" maxThreads="400"  />

 acceptCount="500"：最大的链接数量 
 maxThreads="400" ： 最大的线程数量

3、修改tomcat内存
set JAVA_OPTS= -Xms1024M -Xmx1024M -XX:PermSize=256M -XX:MaxNewSize=256M -XX:MaxPermSize=256M

-Xms1024M：初始化堆内存大小（注意，不加M的话单位是KB）

-Xmx1029M：最大堆内存大小

-XX:PermSize=256M：初始化类加载内存池大小

-XX:MaxPermSize=256M：最大类加载内存池大小

以上流是我们tomcat的常规配置，

如果还有额外的需要操作，可能就是web.xml配置session超时时间，
配置404和500的跳转页面

设置tomcat的编码：

<Connector port="80" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" acceptCount="500" maxThreads="400" 
                URLEncoding="UTF-8"
               />

nginx 集群tiomcat：
nginx：反向代理服务器： 支持20000个同时连接，

首选准备2个独立配置tomcat

这里写图片描述

tomcat1的server.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="alksdjflksajflksaf">
  <Listener className="org.apache.catalina.startup.VersionLoggerListener" />
  <!-- Security listener. Documentation at /docs/config/listeners.html
  <Listener className="org.apache.catalina.security.SecurityListener" />
  -->
  <!--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" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />

  <!-- 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 8080
    -->
    <Connector port="9999" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" acceptCount="500" maxThreads="400" 
                URLEncoding="UTF-8"
               />
    <!-- A "Connector" using the shared thread pool-->
    <!--
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    -->
    <!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the BIO implementation that requires the JSSE
         style configuration. When using the APR/native implementation, the
         OpenSSL style configuration is required as described in the APR/native
         documentation -->
    <!--
    <Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol"
               maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />


    <!-- 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">
    -->
    <Engine name="Catalina" defaultHost="localhost">

      <!--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"/>
      -->

      <!-- Use the LockOutRealm to prevent attempts to guess user passwords
           via a brute-force attack -->
      <Realm className="org.apache.catalina.realm.LockOutRealm">
        <!-- 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"/>
      </Realm>

      <Host name="localhost"  appBase="D:/server/project"
            unpackWARs="true" autoDeploy="true">
        <Context path="" docBase="D:/server/project" reloadable="true"/> 
        <!-- 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
             Note: The pattern used is equivalent to using pattern="common" -->
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log." suffix=".txt"
               pattern="%h %l %u %t &quot;%r&quot; %s %b" />

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

tomcat2的server.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="8006" shutdown="SHUTDOWN">
  <Listener className="org.apache.catalina.startup.VersionLoggerListener" />
  <!-- Security listener. Documentation at /docs/config/listeners.html
  <Listener className="org.apache.catalina.security.SecurityListener" />
  -->
  <!--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" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />

  <!-- 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 8080
    -->
    <Connector port="9998" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8444" />
    <!-- A "Connector" using the shared thread pool-->
    <!--
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    -->
    <!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the BIO implementation that requires the JSSE
         style configuration. When using the APR/native implementation, the
         OpenSSL style configuration is required as described in the APR/native
         documentation -->
    <!--
    <Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol"
               maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8010" protocol="AJP/1.3" redirectPort="8444" />


    <!-- 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">
    -->
    <Engine name="Catalina" defaultHost="localhost">

      <!--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"/>
      -->

      <!-- Use the LockOutRealm to prevent attempts to guess user passwords
           via a brute-force attack -->
      <Realm className="org.apache.catalina.realm.LockOutRealm">
        <!-- 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"/>
      </Realm>

      <Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true">

        <!-- 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
             Note: The pattern used is equivalent to using pattern="common" -->
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log." suffix=".txt"
               pattern="%h %l %u %t &quot;%r&quot; %s %b" />

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

此处注意，所有的端口都要需要修改。

然后配置tomcat1和tomcat2的服务：

tomcat1创建服务并启动： 进入tomcat的bi目录执行service.bat install

这里写图片描述

tomcat2 需要先修改服务的名字，避免和tomcat1重名， 在bin的service.bat用记事本打开，修改为Tomcat8
这里写图片描述

创建tomcat2的服务：
这里写图片描述

然后分别启动tomcat1和tomcat2，命令是 startup.bat
这里写图片描述

可以分别访问测试效果，
http://localhost:9999/ssm/index.html – tomcat1
http://localhost:9998/ssm/index.html –tomcat2

配置nginx：

打开conf下面的nginx.conf文件

这里写图片描述

修改如下配置：

#服务器的集群  
    upstream  xingxue {  #服务器集群名字   
       server localhost:9999  weight=1;#服务器配置 weight是权重的意思，权重越大，分配的概率越大。  
       server localhost:9998  weight=2;  
    }
    server {
        listen       8081;
        server_name  localhost;

        #charset koi8-r;

        #access_log  logs/host.access.log  main;

        location / {
            root   html;
            index  index.html index.htm;
            proxy_pass http://xingxue;  
            proxy_redirect default;  
        }

这里写图片描述

好。集群完成，
输入url： http://localhost:8081/ssm/index.html 访问
此url前面是访问的nginx的服务器， 后面是tomcat下面的项目+资源

多刷新几次，出现如下进入不同的tomcat的页面

这里写图片描述
这里写图片描述

java_esky110
关注
专栏目录
Windows+Nginx+Tomcat搭建负载均衡和集群环境同时实现
11-11
很好的学习Windows+Nginx+Tomcat搭建负载均衡和集群环境教材，里面有详细的Demo。
windows下nginx+tomcat配置负载均衡的方法
01-10
目标：Nginx做为HttpServer，连接多个tomcat应用实例，进行负载均衡。 注：本例程以一台机器为例子，即同一台机器上装一个nginx和2个Tomcat且安装了JDK1.7。 1、安装Nginx 安装Nginx教程 2、配置两个Tomcat 在本机上...
Windows下nginx+tomcat的负载均衡
热门推荐
zls_12的专栏
11-18 7万+
一、为什么需要对Tomcat服务器做负载均衡：  Tomcat服务器作为一个Web服务器，其并发数在300-500之间，如果有超过500的并发数便会出现Tomcat不能响应新的请求的情况，严重影响网站的运行。另外，在访问量大的情况下，Tomcat的线程数会不断增加。由于Tomcat自身对内存的占用有控制，当对内存的占用达到最大值时便会出现内存溢出，对网站的访问严重超时等现象，这时便需要重新启动T
LVS+Nginx高可用集群---搭建高可用集群负载均衡
最新发布
牧夏的个人博客
07-21 772
1.LVS简介Lvs(Virtual Server)：使用集群，对于整个用户来说是透明，用户访问的时候是单个高性能的整体。道理与nginx类似LVS网络拓扑图：是基于四层。用户通过浏览器发送请求，然后到达LVS.Lvs根据相应算法将请求发送到相应的真实的服务器上(RS).
Nginx+Tomcat在Windows下做负载均衡
小董同学
11-30 146
一、 为什么需要对 Tomcat 服务器做负载均衡： Tomcat 服务器作为一个 Web 服务器，其并发数在 300-500 之间，如果有超过 500 的并发数便会出现 Tomcat 不能响应新的请求的情况，严重影响网站的运行。另外，在访问量大的情况下， Tomcat 的线程数会不断增加。由于 Tomcat 自身对内存的占用有控制，当对内存的占用达到最大值时便会出现内存溢出，对网站的访问严...
Nginx+Tomcat集群部署
weixin_34247299的博客
12-10 122
为了获取更好的性能，我们常常需要将tomcat进行集群部署。下文通过nginx转发实现tomcat集群，并通过nginx-upstream-jvm-route插件保证session的粘滞。 　　应用场景环境： 　　server1 服务器上安装了 nginx + tomcat01 　　server2 服务器上只安装了 tomcat02          　　server1 IP 地址： 19...
windows中nginx配置负载均衡
weixin_42169734的博客
05-24 2636
windows中nginx配置负载均衡
Nginx+Tomcat搭建负载均衡，实现网站请求的分发
11-11
Nginx+Tomcat搭建负载均衡，实现网站请求的分发 Nginx+Tomcat搭建负载均衡是实现网站请求的分发的常见解决方案。以下是该解决方案的详细知识点说明： 一、负载均衡的概念 负载均衡是指将网络请求分配到多个服务器...
Nginx+tomcat 实现负载均衡session共享demo
01-05
本教程将详细讲解如何通过`Nginx`实现`Tomcat`集群的负载均衡，并实现`session`共享。 首先，我们要理解负载均衡的基本概念。负载均衡是通过将工作负载分散到多个计算资源，以优化资源使用、最大化吞吐量、最小化...
nginx+tomcat实现负载均衡，使用redis session共享
09-30
本文将介绍如何使用Nginx与Tomcat结合实现负载均衡，并利用Redis进行Session共享，确保用户会话的一致性。 1. **Nginx负载均衡**： Nginx是一款高性能的反向代理服务器，它可以作为Web服务器前端，通过负载均衡...
Windows下使用Nginx+Tomcat做负载均衡的完整步骤
09-29
总结来说，通过以上步骤，我们已经在Windows上成功地配置了Nginx和Tomcat，实现了基于Nginx的负载均衡集群。这种架构不仅能够提高系统的健壮性，还允许在不影响用户服务的情况下，方便地添加或移除Tomcat实例，进行...
nginx windows集群
04-21
windows集群代码~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
nginx负载均衡，基于windows
qq_37361535的博客
01-08 90
1、下载tomcat,https://tomcat.apache.org/download-80.cgi 这边用的是windows 64位的tomcat8 2、下载nginx,http://tengine.taobao.org/nginx_docs/en/download.html 3、将项目放到tomcat,然后复制一个，其中一个tomcat将conf/server.xml中的端口号进行改变，...
Nginx+Tomcat 实现负载均衡（Windows单机测试）
小灯光环
09-06 3822
关于nginx+tomcat实现负载均衡的配置介绍。
Windows系统中配置Nginx负载均衡
qq_41863998的博客
07-01 8460
Windows系统中配置Nginx详细步骤之负载均衡）A.下载nginxB.解压到C盘并开始配置nginx.conf,搭建负载均衡B.1 开始解压文件B.2 配置nginx.conf，搭建负载均衡 A.下载nginx 下载路径：http://nginx.org/en/download.html 这里下载的版本：nginx-1.10.3 B.解压到C盘并开始配置nginx.conf,搭建负载均衡 B.1 开始解压文件 B.2 配置nginx.conf，搭建负载均衡 修改后的截图 修改后的
win下配置nginx负载均衡
qq_36103520的博客
06-02 841
1.下载nginxhttp://nginx.org/en/download.html         下载稳定版本，以nginx/Windows-1.12.2为例，直接下载 nginx-1.12.2.zip下载后解压，解压后如下2.启动nginx有很多种方法启动nginx(1)直接双击nginx.exe，双击后一个黑色的弹窗一闪而过(2)打开cmd命令窗口，切换到nginx解压目录下，输入命令 n...
windows下nginx代理tomcat实现负载均衡配置
slgd的博客
09-13 908
引言：Nginx属于开源免费的负载均衡软件实现方案，跨平台、高效、稳定、配置简单下面案例主要介绍windows平台现nginx作为反向代理服务器，代理2台tomcat配置。 一、下载nginx 官网： http://nginx.org/en/download.html 1.1解压到d盘，D:\nginx\nginx-1.18.0 启动，重启，停止的脚本也是自己创建，方便执行命令 二、tomcat配置 Tomcat以7.0.70为例，例如两台tomcat端口分别是8080,8090 为了在同一电脑上能够同
nginx集群_windows环境下搭建简单Nginx+Tomcat集群
weixin_39562579的博客
11-28 236
通俗点将，负载均衡就是因为访问流量太大，导致项目访问不流畅、甚至宕掉，所以通过一种分流的方式来缓解这种情况。一、 工具nginx-1.8.0apache-tomcat-6.0.33二、 目标实现高性能负载均衡的Tomcat集群：三、 步骤1、首先下载Nginx，要下载稳定版：2、然后解压两个Tomcat，分别命名为apache-tomcat-6.0.33-1和apache-tomcat-6.0.3...
使用Nginx实现Tomcat集群负载均衡配置教程
3. **Nginx+Tomcat负载均衡配置** - **多台Tomcat服务器**：首先，你需要准备两台或更多Tomcat服务器，每台服务器都需要独立运行并配置不同的监听端口，例如18080和28080。 - **端口配置**：在每个Tomcat的`server...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值