[jboss-cvs] JBossAS SVN: r84086 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.

Wed Feb 11 04:13:16 EST 2009

Author: xhuang at jboss.com
Date: 2009-02-11 04:13:16 -0500 (Wed, 11 Feb 2009)
New Revision: 84086

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-11 07:49:24 UTC (rev 84085)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po	2009-02-11 09:13:16 UTC (rev 84086)
@@ -9,8 +9,8 @@
 "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: 2009-02-10 15:33+1000\n"
-"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"PO-Revision-Date: 2009-02-11 19:12+1000\n"
+"Last-Translator: Xi HUANG\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -2153,7 +2153,6 @@
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:783
 #, no-c-format
-#, fuzzy
 msgid ""
 "A good example of such an application is one that makes synchronous group "
 "RPC calls (typically using a JGroups RpcDispatcher.) By synchronous, we mean "
@@ -2161,7 +2160,7 @@
 "members of the group. In that kind of application, the threads on A that are "
 "making calls would block waiting for responses from D, thus naturally "
 "slowing the overall rate of calls."
-msgstr "这样的应用程序"
+msgstr "对于这样的应用程序，一个很好的例子是进行同步组 RPC 调用（通常使用 JGroups RpcDispatcher）的应用程序。同步意味着调用线程在等待所有组成员响应之前一直阻塞。在这种应用程序里，A 上的调用线程将在等待 D 的响应时阻塞，因此自然就降低了总体的调用速度。"
 
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:786
@@ -2493,13 +2492,13 @@
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:907
 #, no-c-format
 msgid "Binding JGroups to the same interface as other services. Simple, just use -b:"
-msgstr ""
+msgstr "把 JGroups 和其他服务一样绑定到相同的接口上。这很简单，只要使用 -b 选项："
 
 #. Tag: screen
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:909
 #, no-c-format
 msgid "./run.sh -b 192.168.1.100 -c all"
-msgstr ""
+msgstr "./run.sh -b 192.168.1.100 -c all"
 
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:913
@@ -2511,6 +2510,8 @@
 "property overrides the -b value. This is a common usage pattern; put client "
 "traffic on one network, with intra-cluster traffic on another."
 msgstr ""
+"把其他服务（如 JBoss Web）绑定到一个接口，但对于 JGroups 使用不同的接口：<screen>./run.sh -b 10.0.0.100 -Djgroups."
+"bind_addr=192.168.1.100 -c all</screen> 设置系统属性来覆盖 -b 指定的值。这是常见的用法：把客户端的通信放在一个网络里，而把群集内部通信放到另外一个网络里。"
 
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:921
@@ -2522,7 +2523,7 @@
 "the machine's default interface. See the Transport Protocols section for how "
 "to tell JGroups to receive or send on all interfaces, if that is what you "
 "really want."
-msgstr ""
+msgstr "把服务（如 JBoss Web）绑定到所有的接口。可以这样实现：<screen>./run.sh -b 0.0.0.0 -c all</screen> 然而，这不会使 JGroups 绑定到所有接口！相反，JGroups 将绑定到主机的缺省接口。关于如何设置 JGroups 在所有接口进行接收或发送，请参考“传输协议”章节。"
 
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:929
@@ -2533,18 +2534,20 @@
 "bind_addr=192.168.1.100 -c all</screen> Again, specifically setting the "
 "system property overrides the -b value."
 msgstr ""
+"把服务（如 JBoss Web）绑定到所有接口，但指定 JGroups 接口：<screen>./run.sh -b 0.0.0.0 -Djgroups."
+"bind_addr=192.168.1.100 -c all</screen> 这里再次设置了系统属性来覆盖 -b 选项的值。"
 
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:937
 #, no-c-format
 msgid "Using different interfaces for different channels:"
-msgstr ""
+msgstr "对于不同的频道使用不同的接口："
 
 #. Tag: screen
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:939
 #, no-c-format
 msgid "./run.sh -b 10.0.0.100 -Djgroups.ignore.bind_addr=true -c all"
-msgstr ""
+msgstr "./run.sh -b 10.0.0.100 -Djgroups.ignore.bind_addr=true -c all"
 
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:944
@@ -2555,12 +2558,14 @@
 "would need to edit the various XML configuration files to set the "
 "<literal>bind_addr</literal> to the desired interfaces."
 msgstr ""
+"这个设置让 JGroups 忽略 <literal>jgroups.bind_addr</"
+"literal> 系统属性，而使用 XML 里指定的值。你需要比编辑 XML 配置文件来把 <literal>bind_addr</literal> 设置为所需的接口。"
 
 #. Tag: title
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:949
 #, no-c-format
 msgid "Isolating JGroups Channels"
-msgstr ""
+msgstr "隔离 JGroups 频道"
 
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:950
@@ -2571,7 +2576,7 @@
 "replication, EJB3 SFSB replication and EJB3 entity replication) along with "
 "the general purpose clustering service called HAPartition that underlies "
 "most other JBossHA services."
-msgstr ""
+msgstr "在 JBoss AS 里有许多独立地创建 JGroups 频道的服务 - 3 个不同的 JBoss Cache 服务（用于 HTTP 会话复制、EJB3 SFSB 复制和 EJB3 entity 复制）以及大多数 JBossHA 服务里底层的通用群集服务 HAPartition。"
 
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:953
@@ -2583,16 +2588,19 @@
 "Nodes improperly communicating with each other is one of the most common "
 "issues users have with JBoss AS clustering."
 msgstr ""
+"这些频道只和所需对点进行通信是很重要的，不要和其他服务使用的频道 "
+"以及用于不是组成员的主机上打开的相同服务的频道通信。节点不正确地和其他节点进行通信是 JBoss AS 群集里最常见的问题之一。"
 
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:956
 #, no-c-format
+#, fuzzy
 msgid ""
 "Whom a JGroups channel will communicate with is defined by its group name, "
 "multicast address, and multicast port, so isolating JGroups channels comes "
 "down to ensuring different channels use different values for the group name, "
 "multicast address and multicast port."
-msgstr ""
+msgstr "JGroups 的组名定义了它将通信的频道。"
 
 #. Tag: para
 #: Clustering_Guide_JBoss_Cache_JGroups.xml:959


