[jboss-cvs] JBossAS SVN: r83872 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Feb 4 23:38:28 EST 2009
Author: xhuang at jboss.com
Date: 2009-02-04 23:38:28 -0500 (Wed, 04 Feb 2009)
New Revision: 83872
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po 2009-02-05 03:18:29 UTC (rev 83871)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po 2009-02-05 04:38:28 UTC (rev 83872)
@@ -1,18 +1,21 @@
+# translation of Clustering_Guide_JBoss_Cache_JGroups.po to
# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
+# Copyright (C) 2007, 2009 Free Software Foundation, Inc.
+#
# Automatically generated, 2007.
-#
+# Xi HUANG <xhuang at redhat.com>, 2009.
msgid ""
msgstr ""
-"Project-Id-Version: JBEAP 420\n"
+"Project-Id-Version: Clustering_Guide_JBoss_Cache_JGroups\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2009-02-05 14:38+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:5
@@ -22,7 +25,7 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:6
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"JGroups and JBossCache provide the underlying communication, node "
"replication and caching services, for JBoss AS clusters. Those services are "
@@ -31,7 +34,7 @@
"session replication etc.)."
msgstr ""
"JGroups 和 JBossCache 为 JBoss AS 群集提供底层的通信，节点复制和缓存服务。这"
-"些服务都配置成 MBeans。对于每一个类型的群集应用程序（如 Stateful Session "
+"些服务都配置为 MBean。对于每一个类型的群集应用程序（如 Stateful Session "
"EJBs， distributed entity EJBs 等），都有一个 JBossCache 和 JGroups 的 "
"MBeans 的集合。"
@@ -175,6 +178,80 @@
" </attribute>\n"
"</mbean> ]]>"
msgstr ""
+"<![CDATA[\n"
+"<mbean code=\"org.jboss.ha.framework.server.ClusterPartition\"\n"
+" name=\"jboss:service=${jboss.partition.name:DefaultPartition}\">\n"
+" \n"
+" ... ...\n"
+" \n"
+" <attribute name=\"PartitionConfig\">\n"
+" <Config>\n"
+" \n"
+" <UDP mcast_addr=\"${jboss.partition."
+"udpGroup:228.1.2.3}\" \n"
+" mcast_port=\"${jboss.hapartition."
+"mcast_port:45566}\"\n"
+" tos=\"8\"\n"
+" ucast_recv_buf_size=\"20000000\"\n"
+" ucast_send_buf_size=\"640000\"\n"
+" mcast_recv_buf_size=\"25000000\"\n"
+" mcast_send_buf_size=\"640000\"\n"
+" loopback=\"false\"\n"
+" discard_incompatible_packets=\"true\"\n"
+" enable_bundling=\"false\"\n"
+" max_bundle_size=\"64000\"\n"
+" max_bundle_timeout=\"30\"\n"
+" use_incoming_packet_handler=\"true\"\n"
+" use_outgoing_packet_handler=\"false\"\n"
+" ip_ttl=\"${jgroups.udp.ip_ttl:2}\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>\n"
+" \n"
+" <PING timeout=\"2000\"\n"
+" down_thread=\"false\" up_thread=\"false\" "
+"num_initial_members=\"3\"/>\n"
+" \n"
+" <MERGE2 max_interval=\"100000\"\n"
+" down_thread=\"false\" up_thread=\"false\" "
+"min_interval=\"20000\"/>\n"
+" <FD_SOCK down_thread=\"false\" up_thread=\"false\"/"
+">\n"
+" \n"
+" <FD timeout=\"10000\" max_tries=\"5\" \n"
+" down_thread=\"false\" up_thread=\"false\" shun="
+"\"true\"/>\n"
+" <VERIFY_SUSPECT timeout=\"1500\" down_thread=\"false"
+"\" up_thread=\"false\"/>\n"
+" <pbcast.NAKACK max_xmit_size=\"60000\"\n"
+" use_mcast_xmit=\"false\" gc_lag=\"0"
+"\"\n"
+" retransmit_timeout="
+"\"300,600,1200,2400,4800\"\n"
+" down_thread=\"false\" up_thread="
+"\"false\"\n"
+" discard_delivered_msgs=\"true\"/>\n"
+" <UNICAST timeout=\"300,600,1200,2400,3600\"\n"
+" down_thread=\"false\" up_thread=\"false\"/"
+">\n"
+" <pbcast.STABLE stability_delay=\"1000\" "
+"desired_avg_gossip=\"50000\"\n"
+" down_thread=\"false\" up_thread="
+"\"false\"\n"
+" max_bytes=\"400000\"/>\n"
+" <pbcast.GMS print_local_addr=\"true\" join_timeout="
+"\"3000\"\n"
+" down_thread=\"false\" up_thread=\"false"
+"\"\n"
+" join_retry_timeout=\"2000\" shun=\"true"
+"\"\n"
+" view_bundling=\"true\"/>\n"
+" <FRAG2 frag_size=\"60000\" down_thread=\"false\" "
+"up_thread=\"false\"/>\n"
+" <pbcast.STATE_TRANSFER down_thread=\"false\" \n"
+" up_thread=\"false\" "
+"use_flush=\"false\"/>\n"
+" </Config>\n"
+" </attribute>\n"
+"</mbean> ]]>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:33
@@ -189,13 +266,13 @@
"is what defines the characteristics of the overall Channel. In the next "
"several sections, we will dig into the commonly used protocols and their "
"options and explain exactly what they mean."
-msgstr ""
+msgstr "JGroups config MBean 属性下的 <Config> 元素包含了所有的 JGroups 配置数据。这些信息被用来配置 JGroups 频道。频道（Channel）从概念上来说和套接字类似，它管理群集里点对点的通信。<Config> 元素里的每个元素都定义了一个 JGroups 协议。每个协议都执行一种功能，这些功能的组合就定义了 overall频道的特征。在下面的章节里，我们将讨论常用的协议及选项并解释其意义。"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:38
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Common Configuration Properties"
-msgstr "其他配置选项"
+msgstr "常见的配置属性"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:39
@@ -203,7 +280,7 @@
msgid ""
"The following common properties are exposed by all of the JGroups protocols "
"discussed below:"
-msgstr ""
+msgstr "下面的常用属性是所有的 JGroups 协议都开放的："
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:43
@@ -219,7 +296,7 @@
"is responsible for reading messages off the queue, doing whatever protocol-"
"specific processing is required, and passing the message on to the next "
"protocol in the stack."
-msgstr ""
+msgstr "<literal>down_thread</literal>：协议是否应该为从更高层传递下来的消息创建一个内部队列和队列处理线程（也称为 down_thread）。更高层可以是栈里的另外一个协议，或者是应用程序本身（如果这个协议已是栈里的顶层）。它如果为 true（缺省值），当消息从更高层传递下来时，调用线程把这个消息放入协议的队列里，然后立即返回。协议的 down_thread 负责从队列里读取消息，完成协议专有的处理，然后把消息传递给栈里下一个协议。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:47
@@ -228,7 +305,7 @@
"<literal>up_thread</literal> is conceptually similar to down_thread, but "
"here the queue and thread are for messages received from lower layers in the "
"protocol stack."
-msgstr ""
+msgstr "<literal>up_thread</literal> 从概念上来说类似于 down_thread，但它的队列和线程用于从更低层传递上来的消息。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:51
@@ -237,6 +314,8 @@
"Generally speaking, <literal>up_thread</literal> and <literal>down_thread</"
"literal> should be set to false."
msgstr ""
+"通常来说，<literal>up_thread</literal> 和 <literal>down_thread</"
+"literal> 都应该设置为 false。"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:57
@@ -311,17 +390,33 @@
" ip_ttl=\"${jgroups.udp.ip_ttl:2}\"\n"
" down_thread=\"false\" up_thread=\"false\"/>]]>"
msgstr ""
+"<![CDATA[\n"
+"<UDP mcast_addr=\"${jboss.partition.udpGroup:228.1.2.3}\" \n"
+" mcast_port=\"${jboss.hapartition.mcast_port:45566}\"\n"
+" tos=\"8\"\n"
+" ucast_recv_buf_size=\"20000000\"\n"
+" ucast_send_buf_size=\"640000\"\n"
+" mcast_recv_buf_size=\"25000000\"\n"
+" mcast_send_buf_size=\"640000\"\n"
+" loopback=\"false\"\n"
+" discard_incompatible_packets=\"true\"\n"
+" enable_bundling=\"false\"\n"
+" max_bundle_size=\"64000\"\n"
+" max_bundle_timeout=\"30\"\n"
+" use_incoming_packet_handler=\"true\"\n"
+" use_outgoing_packet_handler=\"false\"\n"
+" ip_ttl=\"${jgroups.udp.ip_ttl:2}\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>]]>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:75
#, no-c-format
-msgid ""
-"The available attributes in the above JGroups configuration are listed below."
+msgid "The available attributes in the above JGroups configuration are listed below."
msgstr "下列是在上述 JGroups 配置里的可用属性。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:78
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ip_mcast</emphasis> specifies whether or not to use "
"IP multicasting. The default is <literal>true</literal>. If set to false, it "
@@ -329,22 +424,22 @@
"packets are UDP datagrams."
msgstr ""
"<emphasis role=\"bold\">ip_mcast</emphasis> 指定是否使用 IP 多点传送"
-"（multicasting）。它的缺省值是 <literal>true</literal>。"
+"（multicasting）。它的缺省值是 <literal>true</literal>。如果为 false，它将发送 n 个单播数据包而不是一个多点传送数据包。这两种情况都是 UDP 数据包。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:83
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">mcast_addr</emphasis> specifies the multicast "
"address (class D) for joining a group (i.e., the cluster). If omitted, the "
"default is <literal>228.8.8.8 </literal>."
msgstr ""
"<emphasis role=\"bold\">mcast_addr</emphasis> 指定加入到组（就是群集）里的多"
-"点传送地址（class D）。它的缺省值是 <literal>228.8.8.8</literal>。"
+"点传送地址（class D）。它的缺省值是 <literal>228.8.8.8</literal>。 "
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:88
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">mcast_port</emphasis> specifies the multicast port "
"number. If omitted, the default is <literal>45566</literal>."
@@ -354,7 +449,7 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:92
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">bind_addr</emphasis> specifies the interface on "
"which to receive and send multicasts (uses the <literal>-Djgroups."
@@ -365,14 +460,13 @@
"system property is set."
msgstr ""
"<emphasis role=\"bold\">bind_addr</emphasis> 指定接收和发送多点传送的接口（如"
-"果可用，使用 <literal>bind.address</literal> 系统属性）。如果你有一个多宿主主"
-"机，把 <literal>bind_addr</literal> 属性设置为合适的 NIC IP 地址。如果 "
-"<literal>ignore.bind.address</literal> 属性为真（true）的话，这个属性将被忽"
-"略。"
+"果可用，使用 <literal>-Djgroups."
+"bind_address</literal> 系统属性）。如果你有一个多宿主主"
+"机，把 <literal>bind_addr</literal> 属性设置为合适的 NIC IP 地址。在缺省情况下，除非设置了 -Djgroups.ignore.bind_addr 系统属性，系统属性将比 XML 属性具有更高的优先级。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:95
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">receive_on_all_interfaces </emphasis> specifies "
"whether this node should listen on all interfaces for multicasts. The "
@@ -380,10 +474,10 @@
"literal> property for receiving multicasts. However, <literal>bind_addr</"
"literal> (if set) is still used to send multicasts."
msgstr ""
-"<emphasis role=\"bold\">bind_to_all_interfaces</emphasis> 指定是否这个节点应"
+"<emphasis role=\"bold\">receive_on_all_interfaces </emphasis> 指定是否这个节点应"
"该为多点传送侦听所有的接口。它的缺省值是 <literal>false</literal>。它覆盖了接"
"收多点传送的 <literal>bind_addr</literal> 属性。然而，<literal>bind_addr</"
-"literal>（如果设置了）仍会用来发送多点传送信息。"
+"literal>（如果设置了）仍会用来发送多点传送信息。 "
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:100
@@ -392,7 +486,7 @@
"<emphasis role=\"bold\">send_on_all_interfaces</emphasis> specifies whether "
"this node send UDP packets via all the NICs if you have a multi NIC machine. "
"This means that the same multicast message is sent N times, so use with care."
-msgstr ""
+msgstr "<emphasis role=\"bold\">send_on_all_interfaces</emphasis> 指定是否这个节点通过所有的网卡（如果有）发送 UDP 数据包。这表示相同的多点传送消息将被发送 N 次，所以请小心使用。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:105
@@ -404,6 +498,8 @@
"addresses or interface names. E.g. \"<literal>192.168.5.1,eth1,127.0.0.1</"
"literal>\"."
msgstr ""
+"<emphasis role=\"bold\">receive_interfaces</emphasis> 指定接收多点传送消息的接口列表。多点传送接收套接字将侦听所有这些接口。这是一个用逗号隔开的 IP 地址或接口名称的列表。例如：\"<literal>192.168.5.1,eth1,127.0.0.1</"
+"literal>\"。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:111
@@ -414,7 +510,7 @@
"but is actually something of a misnomer, since the value here refers to how "
"many network hops a packet will be allowed to travel before networking "
"equipment will drop it."
-msgstr ""
+msgstr "<emphasis role=\"bold\">ip_ttl</emphasis> 指定 IP 多点传送数据包的 time-to-live。在多点传送网络里，TTL 是一个常用的术语，但实际上算是取名不当，因为这里指的是在网络设备取消数据包之前可以允许的网络 hop 的次数。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:115
@@ -426,22 +522,22 @@
"handler is a separate thread taking care of de-serialization, receiver thread"
"(s) simply put packet in queue and return immediately. Setting this to true "
"adds one more thread. The default is <literal>true</literal>."
-msgstr ""
+msgstr "<emphasis role=\"bold\">use_incoming_packet_handler</emphasis> 指定是否使用独立的线程来处理转入消息。有时候接收者会超载（它们得处理解序列化等）。数据包处理程序是一个独立的线程，它处理解序列化，接收者线程则只需简单地把数据包放入队列并马上返回。把它设置为 true 将增加一个线程。它的缺省值为 <literal>true</literal>。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:118
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">use_outgoing_packet_handler</emphasis> specifies "
"whether to use a separate thread to process outgoing messages. The default "
"is false."
msgstr ""
"<emphasis role=\"bold\">use_outgoing_packet_handler</emphasis> 指定是否使用单"
-"独的线程来处理输出的（outgoing）信息。"
+"独的线程来处理转出消息。缺省值为 false。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:121
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">enable_bundling</emphasis> specifies whether to "
"enable message bundling. If it is <literal>true</literal>, the node would "
@@ -451,7 +547,7 @@
"message and send it. The messages are unbundled at the receiver. The default "
"is <literal>false</literal>."
msgstr ""
-"<emphasis role=\"bold\">enable_bundling</emphasis> 指定是否启用捆绑"
+"<emphasis role=\"bold\">enable_bundling</emphasis> 指定是否启用消息捆绑"
"（bundling）。如果它设为<literal>true</literal>，节点将会把输出的信息排队，一"
"直到积累了 <literal>max_bundle_size</literal> 个字节，或者是 "
"<literal>max_bundle_time</literal> 毫秒后，依哪个先发生而定。然后把排队的信息"
@@ -460,7 +556,7 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:129
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">loopback</emphasis> specifies whether to loop "
"outgoing message back up the stack. In <literal>unicast</literal> mode, the "
@@ -469,11 +565,12 @@
msgstr ""
"<emphasis role=\"bold\">loopback</emphasis> 指定是否在堆栈里回送（loop back）"
"输出信息。在单播 <literal>unicast</literal> 模式下，信息都会发送给自己。如果"
-"是 <literal>mcast</literal> 模式，多点传送信息的备份将被发送。"
+"是 <literal>mcast</literal> 模式，多点传送信息的备份将被发送。它的缺省值是 "
+"<literal>false</literal>。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:134
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">discard_incompatibe_packets</emphasis> specifies "
"whether to discard packets from different JGroups versions. Each message in "
@@ -485,7 +582,8 @@
"<emphasis role=\"bold\">discard_incompatibe_packets</emphasis> 指定是否丢弃从"
"不同版本的 JGroups 过来的数据包。群集里的每个数据包都用 JGroups 版本号来标"
"记。如果它设置为 true，当接收到一个不同 JGroups 版本的信息时，这个信息将被丢"
-"弃; 否则，将记录一个警告。"
+"弃; 否则，将记录一个警告。它的缺省值是 "
+"<literal>false</literal>。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:140
@@ -506,7 +604,7 @@
msgid ""
"<literal>tos</literal> specifies traffic class for sending unicast and "
"multicast datagrams."
-msgstr ""
+msgstr "<literal>tos</literal> 指定发送单播和多点传送数据包的流量类型（traffic class）。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:152
@@ -528,7 +626,7 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:161
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Alternatively, a JGroups-based cluster can also work over TCP connections. "
"Compared with UDP, TCP generates more network traffic when the cluster size "
@@ -543,11 +641,11 @@
"（unicast）的协议。为了发送多点传送的信息，JGroups 使用多个 TCP 单播。如要把 "
"TCP 作为一个传输协议来使用，你应该定义 JGroups <literal>Config</literal> 元素"
"里的 <literal>TCP</literal> 元素。这是一个 <literal>TCP</literal> 元素的例"
-"子。"
+"子。 "
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:167
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<TCP start_port=\"7800\"\n"
" bind_addr=\"192.168.5.1\"\n"
@@ -556,25 +654,25 @@
msgstr ""
"<TCP start_port=\"7800\"\n"
" bind_addr=\"192.168.5.1\"\n"
-" loopback=\"true\"/>"
+" loopback=\"true\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:168
#, no-c-format
-msgid ""
-"Below are the attributes available in the <literal>TCP</literal> element."
+msgid "Below are the attributes available in the <literal>TCP</literal> element."
msgstr "下列是 <literal>TCP</literal> 元素里的可用属性。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:171
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">bind_addr</emphasis> specifies the binding address. "
"It can also be set with the <literal>-Djgroups.bind_address</literal> "
"command line option at server startup."
msgstr ""
"<emphasis role=\"bold\">bind_addr</emphasis> 指定了绑定的地址。它也可以在服务"
-"器启动时用 <literal>-Dbind.address</literal> 命令行选项来设定。"
+"器启动时用 <literal>-Dbind.address</literal> 命令行选项来设定。 "
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:176
@@ -593,10 +691,12 @@
"use MPING or TCPGOSSIP as discovery protocol because <literal>TCCPING</"
"literal> requires listing the nodes and their corresponding ports."
msgstr ""
+"<emphasis role=\"bold\">start_port, end_port</emphasis> 定义了服务器应该绑定的 TCP 端口的范围。服务器套接字绑定到从 <literal>start_port</literal> 开始的第一个可用的端口。如果在 <literal>end_port</literal> 之前没有可用的端口（例如因为防火墙的缘故），服务器将抛出异常。如果没有提供 <literal>end_port</literal> 或者 <literal>end_port < start_port</literal>，那么端口范围就不作限制。如果 <literal>start_port == end_port</literal>，那我们将强迫 JGroups 使用给定的端口（如果端口不可用则会启动失败）。它的缺省值是 7800。如果设置为 0，那么操作系统将选择一个端口。请记住，只有我们使用把 MPING 或 TCPGOSSIP 作为发现协议时才能设置它为 0，因为 <literal>TCCPING</"
+"literal> 要求列出节点以及对应的端口。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:182
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">loopback</emphasis> specifies whether to loop "
"outgoing message back up the stack. In <literal>unicast</literal> mode, the "
@@ -605,18 +705,17 @@
msgstr ""
"<emphasis role=\"bold\">loopback</emphasis> 指定是否在堆栈里回送（loop back）"
"输出信息。在单播 <literal>unicast</literal> 模式下，信息都会发送给自己。如果"
-"是 <literal>mcast</literal> 模式，多点传送信息的备份将被发送。"
+"是 <literal>mcast</literal> 模式，多点传送信息的备份将被发送。它的缺省值是 false。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:187
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">recv_buf_size, send_buf_size</emphasis> define "
"receive and send buffer sizes. It is good to have a large receiver buffer "
"size, so packets are less likely to get dropped due to buffer overflow."
msgstr ""
-"<emphasis role=\"bold\">mcast_send_buf_size，mcast_recv_buf_size，"
-"ucast_send_buf_size，ucast_recv_buf_size</emphasis> 定义接收和发送的缓冲区大"
+"<emphasis role=\"bold\">recv_buf_size, send_buf_size</emphasis> 定义接收和发送的缓冲区大"
"小。设置大的接收缓冲区会比较好，这样数据包就不会因为缓冲区溢出而被丢弃。"
#. Tag: para
@@ -632,7 +731,7 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:195
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">reaper_interval</emphasis> specifies interval (in "
"milliseconds) to run the reaper. If both values are 0, no reaping will be "
@@ -641,7 +740,7 @@
msgstr ""
"<emphasis role=\"bold\">reaper_interval</emphasis> 指定运行 reaper 的时间（毫"
"秒）。如果两个值都是 0，reaper 将不会运行。如果其中一个是 > 0，reaper 将被"
-"启用。"
+"启用。reaper_interval 缺省为 0，表示不运行 reaper。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:200
@@ -651,18 +750,16 @@
"millis for a socket creation. When doing the initial discovery, and a peer "
"hangs, don't wait forever but go on after the timeout to ping other members. "
"Reduces chances of *not* finding any members at all. The default is 2000."
-msgstr ""
+msgstr "<emphasis role=\"bold\">sock_conn_timeout</emphasis> 指定创建套接字的超时时间（毫秒）。当进行初始发现时，如果对点挂起了，在超时后将 ping 其他成员。这减少了找不到任何成员的机会。它的缺省值是 2000。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:203
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">use_send_queues</emphasis> specifies whether to use "
"separate send queues for each connection. This prevents blocking on write if "
"the peer hangs. The default is true."
-msgstr ""
-"<emphasis role=\"bold\">use_incoming_packet_handler</emphasis> 指定是否使用单"
-"独的线程来处理输入的信息。"
+msgstr "<emphasis role=\"bold\">use_send_queues</emphasis> 指定是否为每个连接使用单独的发送队列。如果对点挂起，这防止了线程的阻塞。它的缺省值为 true。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:206
@@ -680,18 +777,16 @@
"node inside the firewall, but only on its external address. Without setting "
"the external_addr, the node behind the firewall will broadcast its private "
"address to the other nodes which will not be able to route to it."
-msgstr ""
+msgstr "<emphasis role=\"bold\">external_addr</emphasis> 指定广播到其他组成员（如果和本地地址不同）时使用的外部 IP 地址。当你使用 NAT（Network Address Translation）时这很有用，例如，对于私有网络里防火墙后的一个节点，但你只能通过外部的可见地址进行路由，这个地址和节点的本地地址不同。因此，你可以配置这个节点来广播其外部地址，同时仍可以绑定本地地址。这避免了使用 TUNNEL 协议（需要中央路由器），因为防火墙外面的节点仍然可以通过外部地址路由至服务器里面的节点。如果不使用 external_addr，其他节点不能通过防火墙后面的节点的私有地址对其进行访问。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:209
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">skip_suspected_members</emphasis> specifies whether "
"unicast messages should not be sent to suspected members. The default is "
"true."
-msgstr ""
-"<emphasis role=\"bold\">ip_mcast</emphasis> 指定是否使用 IP 多点传送"
-"（multicasting）。它的缺省值是 <literal>true</literal>。"
+msgstr "<emphasis role=\"bold\">skip_suspected_members</emphasis> 指定单播消息是否应该被发送到可疑成员。它的缺省值是 <literal>true</literal>。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:212
@@ -704,7 +799,7 @@
"(by setting <literal>enable_bundling</literal> to false). Nagling is "
"disabled by setting <literal>tcp_nodelay</literal> to true. The default is "
"false."
-msgstr ""
+msgstr "<emphasis role=\"bold\">tcp_nodelay</emphasis> 指定 TCP_NODELAY。TCP 缺省使用 Nagles 算法，也就是把小消息捆绑成更大的消息。如果我们想调用同步的群集方法，我们需要禁用 Nagles 并禁用消息捆绑（把 <literal>enable_bundling</literal> 设置为 false）。把 <literal>tcp_nodelay</literal> 设置为 true 可禁用 Nagling。它缺省为 false。"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:220
@@ -714,7 +809,7 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:221
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The TUNNEL protocol uses an external router to send messages. The external "
"router is known as a <literal>GossipRouter</literal>. Each node has to "
@@ -734,18 +829,19 @@
"信。节点可以穿过防火墙（你可以用 80 端口）和 GossipRouter 建立一个 TCP 连接。"
"路由器使用同一个连接来发送信息到防火墙后面的节点。TUNNEL 配置在 JGroups "
"<literal>Config</literal> 元素里的 <literal>TUNNEL</literal> 元素里被定义。下"
-"面是一个例子。"
+"面是一个例子。 "
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:226
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<TUNNEL router_port=\"12001\"\n"
" router_host=\"192.168.5.1\"\n"
" down_thread=\"false\" up_thread=\"false/>"
msgstr ""
"<TUNNEL router_port=\"12001\"\n"
-" router_host=\"192.168.5.1\"/>"
+" router_host=\"192.168.5.1\"\n"
+" down_thread=\"false\" up_thread=\"false/>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:229
@@ -771,8 +867,7 @@
msgid ""
"<emphasis role=\"bold\">router_port</emphasis> specifies the port on which "
"the GossipRouter is listening."
-msgstr ""
-"<emphasis role=\"bold\">router_port</emphasis> 指定 GossipRouter 侦听的端口。"
+msgstr "<emphasis role=\"bold\">router_port</emphasis> 指定 GossipRouter 侦听的端口。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:240
@@ -792,7 +887,7 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:252
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The cluster needs to maintain a list of current member nodes at all times so "
"that the load balancer and client interceptor know how to route their "
@@ -805,14 +900,14 @@
msgstr ""
"群集系统需要一直维护当前成员节点的列表，这样负载平衡系统（load balancer）和客"
"户端拦截器（client interceptor）就知道怎样去指引它们的请求。发现协议"
-"（discovery protocols）用来在群集系统里探索活动节点。当群集系统启动时将检测到"
+"（discovery protocols）用来在群集系统里发现活动节点并检测最老的成员节点。当群集系统启动时将发现"
"所有的初始节点。之后如果有新的节点加入，它只有在组成员协议（group membership "
"protocol）（GMS，参见 <xref linkend=\"jbosscache-jgroups-other-gms\"/>）批准"
-"后才能被探索（discovered）到。"
+"后才能被探索（discovered）到。 "
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:256
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Since the discovery protocols sit on top of the transport protocol, you can "
"choose to use different discovery protocols based on your transport "
@@ -821,7 +916,7 @@
msgstr ""
"既然发现协议（discovery protocols）处于传输协议之上，你可以根据你的传输协议选"
"择不同的发现协议。发现协议在 JGroups MBean <literal>Config</literal> 元素里也"
-"被配置成子元素（sub-elements）。"
+"被配置成子元素（sub-elements）。 "
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:262
@@ -841,31 +936,31 @@
"joiner determines the coordinator from the responses, and sends a JOIN "
"request to it (handled by). If nobody responds, we assume we are the first "
"member of a group."
-msgstr ""
+msgstr "PING 是一个多点传送 PING 请求给 IP 地址或连接 Gossip 路由器的发现协议。PING 通常处于 UDP 或 TUNNEL 传输协议之上。每个节点的都用数据包 {C, A} 进行响应，这里的 C 是协调者（coordinator）的地址而 A 是自己的地址。在超时后或 num_initial_members 个成员进行回复后，Joiner 从响应里决定协调者，并发送 JOIN 请求给它。如果没有节点回应，我们将假设我们是组里的第一个成员。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:266
#, no-c-format
msgid "Here is an example PING configuration for IP multicast."
-msgstr ""
+msgstr "下面是一个用于 IP 多地传送的 PING 配置示例。"
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:270
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<PING timeout=\"2000\"\n"
" num_initial_members=\"2\"\n"
" down_thread=\"false\" up_thread=\"false\"/>"
msgstr ""
"<PING timeout=\"2000\"\n"
-" num_initial_members=\"2\"/>"
+" num_initial_members=\"2\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:271
#, no-c-format
-msgid ""
-"Here is another example PING configuration for contacting a Gossip Router."
-msgstr ""
+msgid "Here is another example PING configuration for contacting a Gossip Router."
+msgstr "下面是另外一个用于联系 Gossip 路由器的 PING 配置示例。"
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:273
@@ -878,6 +973,12 @@
" num_initial_members=\"3\"\n"
" down_thread=\"false\" up_thread=\"false\"/>]]>"
msgstr ""
+"<![CDATA[ \n"
+"<PING gossip_host=\"localhost\"\n"
+" gossip_port=\"1234\"\n"
+" timeout=\"3000\" \n"
+" num_initial_members=\"3\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>]]>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:278
@@ -892,24 +993,23 @@
#: Clustering_Guide_JBoss_Cache_JGroups.xml:329
#: Clustering_Guide_JBoss_Cache_JGroups.xml:358
#: Clustering_Guide_JBoss_Cache_JGroups.xml:392
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">timeout</emphasis> specifies the maximum number of "
"milliseconds to wait for any responses. The default is 3000."
-msgstr ""
-"<emphasis role=\"bold\">timeout</emphasis> 指定等待应答的最长时间（毫秒数）"
+msgstr "<emphasis role=\"bold\">timeout</emphasis> 指定等待应答的最长时间（毫秒数）。缺省为 3000。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:285
#: Clustering_Guide_JBoss_Cache_JGroups.xml:333
#: Clustering_Guide_JBoss_Cache_JGroups.xml:362
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">num_initial_members</emphasis> specifies the maximum "
"number of responses to wait for unless timeout has expired. The default is 2."
msgstr ""
-"<emphasis role=\"bold\">num_initial_members</emphasis> 指定等待的最大的应答数"
-"量。"
+"<emphasis role=\"bold\">num_initial_members</emphasis> 指定除非超时，否则等待的最大的应答数"
+"量。缺省为 2。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:289
@@ -933,13 +1033,13 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:297
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">gossip_refresh</emphasis> specifies the interval (in "
"milliseconds) for the lease from the GossipRouter. The default is 20000."
msgstr ""
"<emphasis role=\"bold\">gossip_refresh</emphasis> 指定 GossipRouter 的租约"
-"（lease）的时间间隔（毫秒数）。"
+"（lease）的时间间隔（毫秒数）。它缺省为 20000。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:301
@@ -1001,7 +1101,7 @@
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:323
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<![CDATA[\n"
"<TCPGOSSIP timeout=\"2000\"\n"
@@ -1009,9 +1109,11 @@
" num_initial_members=\"3\"\n"
" down_thread=\"false\" up_thread=\"false\"/>]]>"
msgstr ""
-"<PING timeout=\"2000\"\n"
-" initial_hosts=\"192.168.5.1[12000],192.168.0.2[12000]\"\n"
-" num_initial_members=\"3\"/>"
+"<![CDATA[\n"
+"<TCPGOSSIP timeout=\"2000\"\n"
+" initial_hosts=\"192.168.5.1[12000],192.168.0.2[12000]\"\n"
+" num_initial_members=\"3\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>]]>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:326
@@ -1054,7 +1156,7 @@
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:352
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<TCPPING timeout=\"2000\"\n"
" initial_hosts=\"hosta[2300],hostb[3400],hostc[4500]\"\n"
@@ -1063,9 +1165,10 @@
" down_thread=\"false\" up_thread=\"false\"/>"
msgstr ""
"<TCPPING timeout=\"2000\"\n"
-" initial_hosts=\"192.168.5.1[7800],192.168.0.2[7800]\"\n"
-" port_range=\"2\"\n"
-" num_initial_members=\"3\"/>"
+" initial_hosts=\"hosta[2300],hostb[3400],hostc[4500]\"\n"
+" port_range=\"3\"\n"
+" num_initial_members=\"3\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:355
@@ -1097,7 +1200,7 @@
"connect to hosta:2300, hosta:2301, hosta:2302, hostb:3400, hostb:3401, "
"hostb:3402, hostc:4500, hostc:4501, hostc:4502. The configuration options "
"allows for multiple nodes on the same host to be pinged."
-msgstr ""
+msgstr "<emphasis role=\"bold\">port_range</emphasis> 指定在获得初始成员资格时探测的连续端口的范围，从参数 initial_hosts 参数开始。给定当前 port_range 和 initial_hosts 为上面的值，TCPPING 层将连接 hosta:2300、 hosta:2301、hosta:2302、hostb:3400、hostb:3401、hostb:3402、hostc:4500、hostc:4501 和 hostc:4502。这个配置选项允许 ping 相同主机上的多个节点。"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:381
@@ -1116,11 +1219,11 @@
"when we want TCP as transport, but multicasting for discovery so we don't "
"have to define a static list of initial hosts in TCPPING or require external "
"Gossip Router."
-msgstr ""
+msgstr "MPING 使用 IP 多点传送来发现初始的成员资格。它可以用于所有的传输协议，但通常是和 TCP 一起使用。TCP 通常要求 TCPPING，它得显性地列出所有的组成员，但 MPING 没有这个要求。典型的用法是当我们把 TCP 作为传输协议但又用多点传送进行发现时，我们不需要在 TCPPING 里定义一个静态的初始主机列表或要求额外的 Gossip Router。"
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:386
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<MPING timeout=\"2000\"\n"
" bind_to_all_interfaces=\"true\"\n"
@@ -1135,7 +1238,8 @@
" mcast_addr=\"228.8.8.8\"\n"
" mcast_port=\"7500\"\n"
" ip_ttl=\"8\"\n"
-" num_initial_members=\"3\"/>"
+" num_initial_members=\"3\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:389
@@ -1147,14 +1251,14 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:396
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">num_initial_members</emphasis> specifies the maximum "
"number of responses to wait for unless timeout has expired. The default is "
"2.."
msgstr ""
-"<emphasis role=\"bold\">num_initial_members</emphasis> 指定等待的最大的应答数"
-"量。"
+"<emphasis role=\"bold\">num_initial_members</emphasis> 指定除非超时，否则要等待的最大的应答数"
+"量。它的缺省值为 2。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:400
@@ -1194,7 +1298,7 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:419
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The failure detection protocols are used to detect failed nodes. Once a "
"failed node is detected, a suspect verification phase can occur after which, "
@@ -1206,7 +1310,7 @@
"故障检测协议（failure detection protocols）用来检测发生故障的节点。一旦检测到"
"了一个发生故障的节点，群集系统会更新它的视图，使负载平衡系统（load balancer）"
"和客户拦截器（client interceptors）避开死节点。故障检测协议被配置为 JGroups "
-"MBean <literal>Config</literal> 元素里的子元素。"
+"MBean <literal>Config</literal> 元素里的子元素。 "
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:425
@@ -1216,7 +1320,7 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:426
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"FD is a failure detection protocol based on heartbeat messages. This "
"protocol requires each node to periodically send are-you-alive messages to "
@@ -1228,12 +1332,11 @@
msgstr ""
"FD 发现协议（FD discovery protocol）要求每个节点定期地发送 are-you-alive 信息"
"给它的邻居节点。如果这个邻居没有应答，呼叫节点将给群集系统发送一个 SUSPECT 信"
-"息。当前的 group coordinator 会复核这个可能有问题的节点是否真的已经崩溃了，并"
-"更新群集系统的视图。这里是一个 FD 配置的例子。"
+"息。当前的组协调者（group coordinator）会复核这个可能有问题的节点是否真的已经崩溃了，如果仍认为它是死节点，就更新群集系统的视图。这里是一个 FD 配置的例子。"
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:430
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<FD timeout=\"2000\"\n"
" max_tries=\"3\"\n"
@@ -1242,7 +1345,8 @@
msgstr ""
"<FD timeout=\"2000\"\n"
" max_tries=\"3\"\n"
-" shun=\"true\"/>"
+" shun=\"true\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:433
@@ -1254,25 +1358,25 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:436
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">timeout</emphasis> specifies the maximum number of "
"milliseconds to wait for the responses to the are-you-alive messages. The "
"default is 3000."
msgstr ""
"<emphasis role=\"bold\">timeout</emphasis> 指定对 are-you-alive 信息的应答的"
-"最长等待时间（毫秒数）。"
+"最长等待时间（毫秒数）。它的缺省值是 3000。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:440
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">max_tries</emphasis> specifies the number of missed "
"are-you-alive messages from a node before the node is suspected. The default "
"is 2."
msgstr ""
"<emphasis role=\"bold\">max_tries</emphasis> 指定在一个节点被怀疑为崩溃前，所"
-"丢失的 are-you-alive 信息的次数。"
+"丢失的 are-you-alive 信息的次数。它的缺省值为 2。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:444
@@ -2160,8 +2264,7 @@
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:831
#, fuzzy, no-c-format
-msgid ""
-"<pbcast.STATE_TRANSFER down_thread=\"false\" up_thread=\"false\"/>"
+msgid "<pbcast.STATE_TRANSFER down_thread=\"false\" up_thread=\"false\"/>"
msgstr ""
"<pbcast.STATE_TRANSFER \n"
" down_thread=\"false\"\n"
@@ -2381,8 +2484,7 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:907
#, no-c-format
-msgid ""
-"Binding JGroups to the same interface as other services. Simple, just use -b:"
+msgid "Binding JGroups to the same interface as other services. Simple, just use -b:"
msgstr ""
#. Tag: screen
@@ -2768,3 +2870,4 @@
"will not process any other messages, including heartbeats, and therefore B "
"will not receive the heartbeat ack and will suspect C."
msgstr ""
+
More information about the jboss-cvs-commits
mailing list