• 人民网舆情分析专家:韩长青 2019-10-15
  • 陕北共产党发起人——李子洲 2019-10-15
  • 迈向命运共同体 开创亚洲新未来 2019-10-11
  • 北京市永定门奥迪中心4S店【在线咨询】 2019-10-11
  • 我发现从五+年代农业用化肥农药,在六+年代几百年长的柿树几乎死光。没人研究! 2019-10-10
  • 游戏成瘾是精神疾病!快看你有没有这些症状 2019-10-10
  • 乌鲁木齐市社会保险管理局社保工作人员开贴,在线解答社 2019-10-02
  • 江西省“放管服”改革再出实招 2019-10-01
  • 抚州发现“一代布王”李璟禧故居 2019-10-01
  • 钱江晚报:火锅店被吃垮,实际是信任破产 2019-09-23
  • 新疆网违法和不良信息举报受理和处置管理办法 2019-09-23
  • 水费欠账竟“穿越”16年?用户质疑:为何没见催缴过? 2019-09-11
  • 青海学习十九大精神嵌套页面--青海频道--人民网 2019-09-11
  • 图片报道:江西省峡江县举行公共租赁住房钥匙发放仪式 2019-09-09
  • 机器人正在敲响未来生活的“大门” 2019-09-09
  • 
    The Apache Tomcat Servlet/JSP Container

    什么平台有玩十三水:Apache Tomcat 7

    Version 7.0.68, Feb 8 2016
    Apache Logo

    qq游戏里有十三水这个游戏吗 www.tdgb.net Links

    Top Level Elements

    Executors

    Connectors

    Containers

    Nested Components

    Cluster Elements

    web.xml

    Other

    The Cluster Receiver object

    Table of Contents
    Introduction

    The receiver component is responsible for receiving cluster messages. As you might notice through the configuration, is that the receiving of messages and sending of messages are two different components, this is different from many other frameworks, but there is a good reason for it, to decouple the logic for how messages are sent from how messages are received.
    The receiver is very much like the Tomcat Connector, its the base of the thread pool for incoming cluster messages. The receiver is straight forward, but all the socket settings for incoming traffic are managed here.

    Blocking vs Non-Blocking Receiver

    The receiver supports both a non blocking, org.apache.catalina.tribes.transport.nio.NioReceiver, and a blocking, org.apache.catalina.tribes.transport.bio.BioReceiver. It is preferred to use the non blocking receiver to be able to grow your cluster without running into thread starvation.
    Using the non blocking receiver allows you to with a very limited thread count to serve a large number of messages. Usually the rule is to use 1 thread per node in the cluster for small clusters, and then depending on your message frequency and your hardware, you'll find an optimal number of threads peak out at a certain number.

    Attributes
    Common Attributes
    AttributeDescription
    className The implementation of the receiver component. Two implementations available, org.apache.catalina.tribes.transport.nio.NioReceiver and org.apache.catalina.tribes.transport.bio.BioReceiver.
    The org.apache.catalina.tribes.transport.nio.NioReceiver is the preferred implementation
    address The address (network interface) to listen for incoming traffic. Same as the bind address. The default value is auto and translates to java.net.InetAddress.getLocalHost().getHostAddress().
    direct Possible values are true or false. Set to true if you want the receiver to use direct bytebuffers when reading data from the sockets.
    port The listen port for incoming data. The default value is 4000. To avoid port conflicts the receiver will automatically bind to a free port within the range of port <= bindPort < port+autoBind So for example, if port is 4000, and autoBind is set to 10, then the receiver will open up a server socket on the first available port in the range 4000-4009.
    autoBind Default value is 100. Use this value if you wish to automatically avoid port conflicts the cluster receiver will try to open a server socket on the port attribute port, and then work up autoBind number of times.
    securePort The secure listen port. This port is SSL enabled. If this attribute is omitted no SSL port is opened up. There default value is unset, meaning there is no SSL socket available.
    udpPort The UDP listen port. If this attribute is omitted no UDP port is opened up. There default value is unset, meaning there is no UDP listener available.
    selectorTimeout The value in milliseconds for the polling timeout in the NioReceiver. On older versions of the JDK there have been bugs, that should all now be cleared out where the selector never woke up. The default value is a very high 5000 milliseconds.
    maxThreads The maximum number of threads in the receiver thread pool. The default value is 6 Adjust this value relative to the number of nodes in the cluster, the number of messages being exchanged and the hardware you are running on. A higher value doesn't mean more efficiency, tune this value according to your own test results.
    minThreads Minimum number of threads to be created when the receiver is started up. Default value is 6
    ooBInline Boolean value for the socket OOBINLINE option. Possible values are true or false.
    rxBufSize The receiver buffer size on the receiving sockets. Value is in bytes, the default value is 43800 bytes.
    txBufSize The sending buffer size on the receiving sockets. Value is in bytes, the default value is 25188 bytes.
    udpRxBufSize The receive buffer size on the datagram socket. Default value is 25188 bytes.
    udpTxBufSize The send buffer size on the datagram socket. Default value is 43800 bytes.
    soKeepAlive Boolean value for the socket SO_KEEPALIVE option. Possible values are true or false.
    soLingerOn Boolean value to determine whether to use the SO_LINGER socket option. Possible values are true or false. Default value is true.
    soLingerTime Sets the SO_LINGER socket option time value. The value is in seconds. The default value is 3 seconds.
    soReuseAddress Boolean value for the socket SO_REUSEADDR option. Possible values are true or false.
    tcpNoDelay Boolean value for the socket TCP_NODELAY option. Possible values are true or false. The default value is true
    timeout Sets the SO_TIMEOUT option on the socket. The value is in milliseconds and the default value is 3000 milliseconds.
    useBufferPool Boolean value whether to use a shared buffer pool of cached org.apache.catalina.tribes.io.XByteBuffer objects. If set to true, the XByteBuffer that is used to pass a message up the channel, will be recycled at the end of the requests. This means that interceptors in the channel must not maintain a reference to the object after the org.apache.catalina.tribes.ChannelInterceptor#messageReceived method has exited.
    NioReceiver
    BioReceiver
    Comments

    Notice: This comments section collects your suggestions on improving documentation for Apache Tomcat.

    If you have trouble and need help, read Find Help page and ask your question on the tomcat-users qq游戏里有十三水这个游戏吗. Do not ask such questions here. This is not a Q&A section.

    The Apache Comments System is explained here. Comments may be removed by our moderators if they are either implemented or considered invalid/off-topic.


    Copyright © 1999-2016, Apache Software Foundation
  • 人民网舆情分析专家:韩长青 2019-10-15
  • 陕北共产党发起人——李子洲 2019-10-15
  • 迈向命运共同体 开创亚洲新未来 2019-10-11
  • 北京市永定门奥迪中心4S店【在线咨询】 2019-10-11
  • 我发现从五+年代农业用化肥农药,在六+年代几百年长的柿树几乎死光。没人研究! 2019-10-10
  • 游戏成瘾是精神疾病!快看你有没有这些症状 2019-10-10
  • 乌鲁木齐市社会保险管理局社保工作人员开贴,在线解答社 2019-10-02
  • 江西省“放管服”改革再出实招 2019-10-01
  • 抚州发现“一代布王”李璟禧故居 2019-10-01
  • 钱江晚报:火锅店被吃垮,实际是信任破产 2019-09-23
  • 新疆网违法和不良信息举报受理和处置管理办法 2019-09-23
  • 水费欠账竟“穿越”16年?用户质疑:为何没见催缴过? 2019-09-11
  • 青海学习十九大精神嵌套页面--青海频道--人民网 2019-09-11
  • 图片报道:江西省峡江县举行公共租赁住房钥匙发放仪式 2019-09-09
  • 机器人正在敲响未来生活的“大门” 2019-09-09
  • 手机投注彩票大奖 香港六彩马经特码资料 欢乐生肖官方开奖号码结果 下载爱宝贝早教全计划 太子中心稳赚六肖 快乐时时是全国开奖 6肖中特是什么意思 北京赛车pk10 炸金花 极速11选5的和值双 复式投注计算 斗地主(单机版) 今晚六开彩开奖结资料 广西十一选五前三直选 22选5黑龙江走势图片