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

[jboss-cvs-commits at lists.jboss.org]

Author: xhuang at jboss.com
Date: 2009-01-22 00:54:48 -0500 (Thu, 22 Jan 2009)
New Revision: 83233

Modified:
   projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_Introduction.po
Log:
update

Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_Introduction.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_Introduction.po	2009-01-22 05:48:36 UTC (rev 83232)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_Introduction.po	2009-01-22 05:54:48 UTC (rev 83233)
@@ -1,34 +1,40 @@
+# translation of Clustering_Guide_Introduction.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_Introduction\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-01-22 15:54+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_Introduction.xml:5
 #, no-c-format
+#, fuzzy
 msgid "Clustering"
 msgstr "群集"
 
 #. Tag: subtitle
 #: Clustering_Guide_Introduction.xml:6
 #, no-c-format
+#, fuzzy
 msgid "High Availability Enterprise Services via JBoss Clusters"
 msgstr "用 JBoss 群集实现高可用性企业服务"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:9
 #, no-c-format
+#, fuzzy
 msgid "Introduction"
 msgstr "简介"
 
@@ -54,6 +60,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:14
 #, no-c-format
+#, fuzzy
 msgid ""
 "The JBoss Application Server (AS) comes with clustering support out of the "
 "box. The simplest way to start a JBoss server cluster is to start several "
@@ -83,12 +90,14 @@
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:23
 #, no-c-format
+#, fuzzy
 msgid "Cluster Definition"
 msgstr "群集系统的定义"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:24
 #, no-c-format
+#, fuzzy
 msgid ""
 "A cluster is a set of nodes that communicate with each other and work toward "
 "a common goal. In a JBoss Application Server cluster (also known as a "
@@ -106,11 +115,12 @@
 "and name that matches the other cluster members. In summary, a JBoss cluster "
 "is a set of AS server instances each of which is running an identically "
 "configured and named JGroups Channel."
-msgstr ""
+msgstr "群集系统是节点（nodeï¼‰çš„é›†åˆï¼Œå®ƒä»¬å½¼æ­¤é€šä¿¡å¹¶å®žçŽ°å…±åŒçš„ç›®æ ‡ã€‚åœ¨ JBoss 群集（也称为 \"partition\"）里，节点是一个 JBoss 服务器实例。节点间的通信由 JGroups group çš„ communication 库来处理，而 JGroups Channel æä¾›æ ¸å¿ƒçš„åŠŸèƒ½ï¼Œå®ƒè·Ÿè¸ªç¾¤é›†é‡Œæœ‰ä»€ä¹ˆèŠ‚ç‚¹å¹¶åœ¨èŠ‚ç‚¹é—´å¯é åœ°äº¤æ¢æ¶ˆæ¯ã€‚å…·æœ‰ç›¸åŒé…ç½®å’Œåç§°çš„ JGroups Channel 能够动态地发行彼此并组成一个组。这就是为什么在同一网络里简单地执行“run -c all”启动两个 AS 实例就能组成群集 - 每个 AS 都启动了一个带有相同缺省配置的 Channelï¼ˆå®žé™…ä¸Šæ˜¯å‡ ä¸ªï¼‰ï¼Œæ‰€ä»¥å®ƒä»¬å¯ä»¥åŠ¨æ€åœ°å‘çŽ°å¯¹æ–¹å¹¶ç»„æˆç¾¤é›†ã€‚åœ¨ä»»ä½•æ—¶å€™èŠ‚ç‚¹éƒ½å¯ä»¥åŠ¨æ€åœ°æ·»åŠ åˆ°ç¾¤é›†æˆ–ä»Žç¾¤é›†åˆ é™¤ï¼Œè¿™åªè¦å¯åŠ¨æˆ–åœæ­¢ç¬¦åˆå…¶ä»–ç¾¤é›†æˆå‘˜çš„é…ç½®å’Œåç§°çš„ Channel 就可以了。总而言之，JBoss 群集是一系列 AS 服务器实例的集合，每个都以相同配置å’!
 Œåç§°çš„ JGroups Channel 运行。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:29
 #, no-c-format
+#, fuzzy
 msgid ""
 "On the same AS instance, different services can create their own Channel. In "
 "a default 5.0.x AS, four different services create channels – the web "
@@ -119,7 +129,7 @@
 "as HAPartition. In order to differentiate these channels, each must have a "
 "unique name, and its configuration must match its peers yet differ from the "
 "other channels."
-msgstr ""
+msgstr "HAPartition."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:32
@@ -135,6 +145,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:36
 #, no-c-format
+#, fuzzy
 msgid ""
 "On the same network, even for the same service, we may have different "
 "clusters. <xref linkend=\"clustering-Partition.fig\"/> shows an example "
@@ -143,17 +154,19 @@
 "simply by configuring the AS instances such that within a set of nodes meant "
 "to form a cluster the Channel configurations and names match while they "
 "differ from any other channels on the same network."
-msgstr ""
+msgstr "在相同的网络上，即使是对于相同的服务，都可能有不同的群集。<xref linkend=\"clustering-Partition.fig\"/> 显示了一个分成三个群集的 JBoss 服务器实例网络，第三个群集只有一个节点。这种拓扑结构可以通过简单地配置 AS 实例来设立，对于要为了组成群集的频道，它们的配置和名称相同但和相同网络上的其他频道不同。"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:38
 #, no-c-format
+#, fuzzy
 msgid "Clusters and server nodes"
-msgstr "Clusters and server nodes"
+msgstr "群集和服务器节点"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:46
 #, no-c-format
+#, fuzzy
 msgid ""
 "The section on “JGroups Configuration” and on “Isolating JGroups Channels” "
 "covers in detail how to configure Channels such that desired peers find each "
@@ -162,17 +175,19 @@
 "categories: the Channel used by the general purpose HAPartition service, and "
 "three Channels created by JBoss Cache for special purpose caching and "
 "cluster wide state replication."
-msgstr ""
+msgstr "“JGroups 配置”和“隔离 JGroups é¢‘é“â€ç« èŠ‚ä»‹ç»äº†å¦‚ä½•é…ç½®é¢‘é“çš„ç»†èŠ‚ï¼Œä¾‹å¦‚æ€Žæ ·æ‰¾åˆ°æ‰€éœ€ç«¯ç‚¹è€Œå¿½ç•¥ä¸éœ€è¦çš„ç«¯ç‚¹ã€‚å¦‚å‰æ‰€è¿°ï¼ŒJBoss AS 缺省使用 4 个独立的 JGroups 频道。它们分成两个类别：通用的 HAPartition 服务使用的频道和 JBoss Cache 创建的用于特殊目的（如缓存和状态复制）的 3 个频道。"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:50
 #, no-c-format
+#, fuzzy
 msgid "HAPartition"
-msgstr ""
+msgstr "HAPartition"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:52
 #, no-c-format
+#, fuzzy
 msgid ""
 "HAPartition is a general purpose service used for a variety of tasks in AS "
 "clustering. At its core, it is an abstraction built on top of a JGroups "
@@ -185,7 +200,7 @@
 "rest of this guide, including smart client-side clustered proxies, EJB 2 "
 "SFSB replication and entity cache management, farming, HA-JNDI and HA "
 "singletons."
-msgstr ""
+msgstr "HAPartition 是 AS 群集里各种任务使用的通用服务。它是构建在 JGroups 频道上的绝对层，提供对从一个或多个群集成员创建/接收 RPC 调用的支持。HAPartition ä¹Ÿæ”¯æŒåˆ†å¸ƒå¼çš„è¿è¡Œåœ¨æ¯ä¸ªç¾¤é›†æˆå‘˜ä¸Šçš„ç¾¤é›†æœåŠ¡æ³¨å†Œè¡¨ã€‚å½“ç¾¤é›†æˆå‘˜èµ„æ ¼æˆ–è€…ç¾¤é›†æœåŠ¡æ³¨å†Œå‘ç”Ÿå˜åŠ¨æ—¶ï¼Œå®ƒä¸ºæ„Ÿå…´è¶£çš„ Listener 提供通知。HAPartition æ˜¯è®¸å¤šç¾¤é›†æœåŠ¡çš„æ ¸å¿ƒç»„æˆéƒ¨åˆ†ï¼Œå¦‚æ™ºèƒ½å®¢æˆ·ç«¯ç¾¤é›†ä»£ç†ï¼ˆSmart Client-side Clustered Proxies）、EJB2 SFSB 复制和实体缓存管理、Farming、HA-JNDI å’Œ HA 单点登录，我们将在本指南的后面部分进行讨论。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:58
@@ -197,13 +212,13 @@
 "network, you would get a default cluster named <literal>DefaultPartition</"
 "literal> that includes all server instances as its nodes."
 msgstr ""
-"ä¸‹ä¾‹å±•ç¤ºäº†æ ‡å‡† JBoss AS 发行版本里的 MBean çš„å®šä¹‰ã€‚å¦‚æžœä½ åœ¨æœ¬åœ°ç½‘ç»œé‡Œç”¨ç¼ºçœçš„"
-"群集设定来启动  JBoss æœåŠ¡å™¨ï¼Œä½ å°†å¾—åˆ°ä¸€ä¸ªå« <literal>DefaultPartition</"
+"ä¸‹ä¾‹å±•ç¤ºäº†æ ‡å‡† JBoss AS 发行版本里的 <literal>HAPartition</literal> MBean çš„å®šä¹‰ã€‚å¦‚æžœä½ åœ¨æœ¬åœ°ç½‘ç»œé‡Œç”¨ç¼ºçœçš„ç¾¤é›†è®¾å®šæ¥å¯åŠ¨  JBoss æœåŠ¡å™¨ï¼Œä½ å°†å¾—åˆ°ä¸€ä¸ªå« <literal>DefaultPartition</"
 "literal> 的缺省群集，它包括了所有作为节点的服务器实例。"
 
 #. Tag: programlisting
 #: Clustering_Guide_Introduction.xml:62
 #, no-c-format
+#, fuzzy
 msgid ""
 "&lt;mbean code=\"org.jboss.ha.framework.server.ClusterPartition\"\n"
 "    name=\"jboss:service=DefaultPartition\"&gt;\n"
@@ -265,10 +280,8 @@
 "jgroups\"/>. The following list shows the available configuration attributes "
 "in the <literal>HAPartition</literal> MBean."
 msgstr ""
-"在这里，我们忽略了这个群集的详细的 JGroups 协议配置（protocal "
-"configuration）。JGroups 处理节点之间底层的点到点通信，我们将在 <xref "
-"linkend=\"jbosscache-jgroups\"/> 里讨论它的配置。下面的列表展示了 "
-"<literal>ClusterPartition</literal> MBean 里可用的配置属性。"
+"在这里，我们忽略了这个频道的详细的 JGroups 协议配置。JGroups 处理节点之间底层的点到点通信，我们将在 <xref linkend=\"jbosscache-jgroups\"/> 里讨论它的配置。下面的列表展示了 "
+"<literal>HAPartition</literal> MBean 里可用的配置属性。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:68
@@ -280,7 +293,7 @@
 "--partition) command line switch to set this value at JBoss startup."
 msgstr ""
 "<emphasis role=\"bold\">PartitionName</emphasis> 是用来指定节点名称的可选属"
-"性。它的缺省值是 <literal>DefaultPartition</literal>。"
+"性。它的缺省值是 <literal>DefaultPartition</literal>。使用 <literal>-g </literal>（等于 --partition）命令行选项可在 JBoss 启动时设置它的值。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:72
@@ -288,13 +301,12 @@
 msgid ""
 "<emphasis role=\"bold\">NodeAddress</emphasis> is an optional attribute used "
 "to help generate a unique name for this node."
-msgstr ""
-"<emphasis role=\"bold\">NodeAddress</emphasis> 是用来指定节点所绑定的 IP 地址"
-"的可选属性。"
+msgstr "<emphasis role=\"bold\">NodeAddress</emphasis> 是为节点生成唯一名称的可选属性。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:75
 #, no-c-format
+#, fuzzy
 msgid ""
 "<emphasis role=\"bold\">DeadlockDetection</emphasis> is an optional boolean "
 "attribute that tells JGroups to run message deadlock detection algorithms "
@@ -315,12 +327,12 @@
 "service startup. Its default value is <literal>30000</literal>."
 msgstr ""
 "<emphasis role=\"bold\">StateTransferTimeout</emphasis> 是用来指定跨群集的状"
-"态复制（state replication）的超时时间（以毫秒为单位）的可选属性。它的缺省值"
-"是 <literal>30000</literal>。"
+"态复制（state replication）的超时时间（以毫秒为单位）的可选属性。状态复制指的是在服务启动时从其他运行的群集成员获取应用程序初始状态的过程。它的缺省值是 <literal>30000</literal>。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:83
 #, no-c-format
+#, fuzzy
 msgid ""
 "<emphasis role=\"bold\">PartitionConfig</emphasis> is an element to specify "
 "JGroup configuration options for this cluster (see <xref linkend="
@@ -333,12 +345,13 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:87
 #, no-c-format
+#, fuzzy
 msgid ""
 "In order for nodes to form a cluster, they must have the exact same "
 "<literal>PartitionName</literal> and the <literal>ParitionConfig</literal> "
 "elements. Changes in either element on some but not all nodes would cause "
 "the cluster to split."
-msgstr ""
+msgstr "为了组成群集，节点必须具有相同的 <literal>PartitionName</literal> å’Œ <literal>ParitionConfig</literal> å…ƒç´ ã€‚å¯¹ä¸€äº›è€Œéžå…¨éƒ¨èŠ‚ç‚¹çš„è¿™ä¸ªä¸¤ä¸ªå…ƒç´ çš„ä¿®æ”¹ä¼šå¯¼è‡´ç¾¤é›†åˆ†ç¦»ã€‚"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:90
@@ -354,9 +367,7 @@
 msgstr ""
 "ä½ å¯ä»¥ç”¨æµè§ˆå™¨è®¿é—®ç¾¤é›†ç³»ç»Ÿé‡Œçš„ä»»ä½• JBoss 实例的 JMX 控制台来查看当前的群集信"
 "息（如，<literal>http://hostname:8080/jmx-console/</literal>），点击 "
-"<literal>jboss:service=DefaultPartition</literal> MBeanï¼ˆå¦‚æžœè¿™ä¸ªèŠ‚ç‚¹æ²¡æœ‰åŠ "
-"å…¥ <literal>DefaultPartition</literal>ï¼Œä½ å¯ä»¥æ”¹å˜ MBean åæ¥åæ˜ ç¾¤é›†åï¼‰ã€‚"
-"<literal>CurrentView</literal> 字段会显示当前群集的 IP 地址的列表。"
+"<literal>jboss:service=DefaultPartition</literal> MBeanï¼ˆå¦‚æžœä½ ä½¿ç”¨äº† -g å¯åŠ¨é€‰é¡¹ï¼Œä½ å¯ä»¥æ”¹å˜ MBean åæ¥åæ˜ ç¾¤é›†åï¼‰ã€‚<literal>CurrentView</literal> 字段会显示当前群集的 IP 地址的列表。"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:94 Clustering_Guide_Introduction.xml:398
@@ -367,7 +378,7 @@
 #: Clustering_Guide_Introduction.xml:2478
 #, fuzzy, no-c-format
 msgid "Note"
-msgstr "备注"
+msgstr "备注 "
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:95
@@ -377,14 +388,14 @@
 "multiple HAPartitions at the same time, this practice is generally not "
 "recommended, as it increases management complexity."
 msgstr ""
-"从技术上来讲，我们可以在同一时间把 JBoss 服务器实例放到多个群集里，但我们通常"
+"从技术上来讲，我们可以在同一时间把 JBoss 服务器实例放到多个 HAPartition 里，但我们通常"
 "ä¸æŽ¨èè¿™ä¹ˆåšï¼Œå› ä¸ºè¿™å¢žåŠ äº†ç®¡ç†çš„å¤æ‚æ€§ã€‚"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:101
 #, fuzzy, no-c-format
 msgid "JBoss Cache channels"
-msgstr "JBoss XMBeans"
+msgstr "JBoss Cache 频道"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:102
@@ -398,15 +409,14 @@
 "cover those MBeans when we discuss specific services in the next several "
 "sections."
 msgstr ""
-"JBoss Cache 是个一个能用在任何应用程序和独立服务器环境里的分布式缓存框架。它"
-"逐渐地代替了 <literal>HASessionState</literal> 服务。JBoss AS 集成了 JBoss "
+"JBoss Cache 是个一个能用在任何应用程序和独立服务器环境里的分布式缓存框架。JBoss AS 集成了 JBoss "
 "Cache 来为 HTTP 会话，EJB 3.0，entity beans 和 Hibernate 持久化对象 "
-"（persistence objects） 提供缓存服务，每个缓存服务都在不同的 MBean 里定义。我"
-"们将在后面讨论特定服务时介绍这些 MBean。"
+"（persistence objects） 提供缓存服务，每个缓存服务都在不同的 MBean 里定义，每个缓存都创建自己的 JGroups 频道。我们将在后面讨论特定服务时介绍这些 MBean。"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:107
 #, no-c-format
+#, fuzzy
 msgid "Service Architectures"
 msgstr "服务架构"
 
@@ -422,17 +432,17 @@
 "k.a smart proxies or stubs) and external load balancers. Which architecture "
 "your application will use will depend on what type of client you have."
 msgstr ""
-"每个节点上的 <literal>ClusterPartition</literal> MBean 定义的群集拓扑结构"
+"每个节点上的 <literal>HAPartition</literal> MBean 定义的群集拓扑结构"
 "（clustering topography）对系统管理员很重要。但是对于大部分的应用程序开发者来"
 "è¯´ï¼Œä½ å¯èƒ½æ›´å…³å¿ƒä»Žå®¢æˆ·åº”ç”¨ç¨‹åºçš„è§’åº¦æ¥çœ‹çš„ç¾¤é›†æž¶æž„ã€‚JBoss AS 支持两种群集架"
-"构：客户端拦截器（client-side interceptors）（proxies 或 stubs）和负载平衡系"
-"统（load balancers）。"
+"构：客户端拦截器（client-side interceptors）（也称为 smart proxies 或 stubs）和负载平衡系"
+"统（load balancers）。选用哪种架构取决于客户端的类型。"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:114 Clustering_Guide_Introduction.xml:160
 #, fuzzy, no-c-format
 msgid "Client-side interceptor architecture"
-msgstr "客户端拦截器"
+msgstr "客户端拦截器架构"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:115
@@ -475,7 +485,7 @@
 "clustering architecture is illustrated in <xref linkend=\"clustering-"
 "InterceptorArch.fig\"/>."
 msgstr ""
-"stub interceptors 拥有群集系统的更新信息。例如，它们知道所有可用网络节点的 "
+"这些 stub 拦截器拥有群集系统的更新信息。例如，它们知道所有可用网络节点的 "
 "IP åœ°å€ï¼Œæ€Žæ ·åœ¨èŠ‚ç‚¹ä¸Šåˆ†æ‘Šè´Ÿè½½çš„ç®—æ³•ï¼ˆè¯·å‚è€ƒä¸‹ä¸€éƒ¨åˆ†å†…å®¹ï¼‰ï¼Œå’Œå¦‚æžœç›®æ ‡èŠ‚ç‚¹ä¸å¯"
 "用时对请求进行失效切换（failover）。对于每个服务请求，服务器节点都用群集里最"
 "新的信息来更新 stub interceptor。例如，如果一个节点退出群集系统后，每个客户 "
@@ -486,12 +496,14 @@
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:123
 #, no-c-format
+#, fuzzy
 msgid "The client-side interceptor (proxy) architecture for clustering"
 msgstr "The client-side interceptor (proxy) architecture for clustering"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:131
 #, no-c-format
+#, fuzzy
 msgid ""
 "describes how to enable the client proxy to handle the entire cluster "
 "restart."
@@ -500,6 +512,7 @@
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:136
 #, no-c-format
+#, fuzzy
 msgid "Load balancer"
 msgstr "负载平衡系统"
 
@@ -527,16 +540,18 @@
 msgstr ""
 "其他的 JBoss 服务，特别是 HTTP web 服务，不要求客户下载任何东西。客户端（如，"
 "web 浏览器）按照某种通信协议（如 HTTP 协议）直接发送请求和接收回复。在这种情"
-"况下，负载平衡系统需要处理所有的请求并把它们分配给群集里的服务器节点。负载平"
-"衡系统是群集里的一个典型概念。它理解群集配置和失效切换策略（failover "
-"policies）。客户只需要知道它的存在。<xref linkend=\"clustering-BalancerArch."
-"fig\"/> 说明了负载平衡系统的群集架构。"
+"况下，负载平衡系统需要处理所有的请求并把它们分配给群集里的服务器节点。 "
+"客户端只需要知道如何和负载平衡系统通信就可以了；它不需要了解负载平衡系统后面的 JBoss AS 实例。"
+"è´Ÿè½½å¹³è¡¡ç³»ç»Ÿä»Žé€»è¾‘ä¸Šæ¥è¯´æ˜¯ç¾¤é›†çš„ä¸€éƒ¨åˆ†ï¼Œä½†æˆ‘ä»¬ä¹‹æ‰€ä»¥å°†å…¶ç§°ä¸ºâ€œå¤–éƒ¨çš„â€ï¼Œæ˜¯å› ä¸ºå®ƒæ²¡æœ‰è¿è¡Œåœ¨å’Œå®¢æˆ·ç«¯æˆ–ä»»ä½• JBoss AS 实例相同的进程里。负载平衡系统可以用软件也可以用硬件实现。市场上有许多硬件负载平衡系统的供应商；mod_jk Apache 模块是一个优秀的软件负载平衡系统。"
+"外部的负载平衡系统理解群集配置和失效切换策略（failover "
+"policies）并实现自己的机制。<xref linkend=\"clustering-BalancerArch."
+"fig\"/> 说明了外部负载平衡系统的群集架构。"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:141
 #, fuzzy, no-c-format
 msgid "The external load balancer architecture for clustering"
-msgstr "The load balancer architecture for clustering"
+msgstr "用于群集的外部负载平衡系统"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:148
@@ -548,11 +563,12 @@
 "services."
 msgstr ""
 "负载平衡系统的一个潜在问题就是它本身就是单一的故障点。它需要被很好地监控来确"
-"保整个群集服务的高可用性。"
+"保整个群集服务的高可用性。 "
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:155
 #, no-c-format
+#, fuzzy
 msgid "Load-Balancing Policies"
 msgstr "负载平衡策略"
 
@@ -566,7 +582,7 @@
 "policies available in JBoss AS."
 msgstr ""
 "JBoss 客户端拦截器（stub）和负载平衡系统都使用了负载平衡策略来决定把新请求发"
-"送给哪个节点。让我们来看看 JBoss AS 里的负载平衡策略。"
+"送给哪个节点。让我们来看看 JBoss AS 里的负载平衡策略。 "
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:161
@@ -588,7 +604,7 @@
 "the list."
 msgstr ""
 "Round-Robin (<literal>org.jboss.ha.framework.interfaces.RoundRobin</"
-"literal>)ï¼šæ¯æ¬¡è°ƒç”¨éƒ½åˆ†æ´¾ç»™æ–°èŠ‚ç‚¹ã€‚ç¬¬ä¸€ä¸ªç›®æ ‡èŠ‚ç‚¹ä»Žåˆ—è¡¨é‡Œéšæœºé€‰æ‹©ã€‚"
+"literal>)ï¼šæ¯æ¬¡è°ƒç”¨éƒ½åˆ†æ´¾ç»™æ–°èŠ‚ç‚¹ã€‚ç¬¬ä¸€ä¸ªç›®æ ‡èŠ‚ç‚¹ä»Žåˆ—è¡¨é‡Œéšæœºé€‰æ‹©ã€‚ "
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:172
@@ -598,7 +614,7 @@
 "literal>): for each call the target node is randomly selected from the list."
 msgstr ""
 "Round-Robin (<literal>org.jboss.ha.framework.interfaces.RoundRobin</"
-"literal>)ï¼šæ¯æ¬¡è°ƒç”¨éƒ½åˆ†æ´¾ç»™æ–°èŠ‚ç‚¹ã€‚ç¬¬ä¸€ä¸ªç›®æ ‡èŠ‚ç‚¹ä»Žåˆ—è¡¨é‡Œéšæœºé€‰æ‹©ã€‚"
+"literal>)ï¼šæ¯æ¬¡è°ƒç”¨éƒ½ä»Žåˆ—è¡¨é‡Œéšæœºé€‰æ‹©ç›®æ ‡èŠ‚ç‚¹ã€‚"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:177
@@ -620,7 +636,7 @@
 "literal>)ï¼šé€‰æ‹©å…¶ä¸­ä¸€ä¸ªå¯ç”¨ç›®æ ‡èŠ‚ç‚¹ä½œä¸ºä¸»ç›®æ ‡èŠ‚ç‚¹ï¼Œç”¨äºŽæ¯æ¬¡è°ƒç”¨ï¼šè¿™ä¸ªèŠ‚ç‚¹æ˜¯åœ¨"
 "ç¾¤é›†é‡Œçš„èŠ‚ç‚¹åˆ—è¡¨é‡Œéšæœºé€‰å–çš„ã€‚å½“ç›®æ ‡èŠ‚ç‚¹çš„åˆ—è¡¨æ”¹å˜æ—¶ï¼ˆå› ä¸ºæœ‰èŠ‚ç‚¹å¯åŠ¨æˆ–é€€"
 "å‡ºï¼‰ï¼Œé™¤éžå½“å‰é€‰ç”¨çš„èŠ‚ç‚¹ä»ç„¶å¯ç”¨ï¼Œè¿™ä¸ªç­–ç•¥ä¼šé‡æ–°é€‰æ‹©ä¸€ä¸ªç›®æ ‡èŠ‚ç‚¹ã€‚æ¯ä¸ªå®¢æˆ·ç«¯"
-"æ‹¦æˆªå™¨æˆ–è€…è´Ÿè½½å¹³è¡¡ç³»ç»Ÿéƒ½ä¼šæ ¹æ®è‡ªå·±çš„ç­–ç•¥ç‹¬ç«‹åœ°é€‰æ‹©ç›®æ ‡èŠ‚ç‚¹ã€‚"
+"æ‹¦æˆªå™¨æˆ–è€…è´Ÿè½½å¹³è¡¡ç³»ç»Ÿéƒ½ä¼šæ ¹æ®è‡ªå·±çš„ç­–ç•¥ç‹¬ç«‹åœ°é€‰æ‹©ç›®æ ‡èŠ‚ç‚¹ï¼Œæ‰€ä»¥å¦‚æžœæŸä¸ªå®¢æˆ·ç«¯ä»Žç›¸åŒçš„ç›®æ ‡æœåŠ¡ï¼ˆå¦‚ EJB）下载两个 stub 时，每个 stub éƒ½å°†ç‹¬ç«‹åœ°é€‰å–è‡ªå·±çš„ç›®æ ‡èŠ‚ç‚¹ã€‚æ—¢ç„¶ç›®æ ‡èŠ‚ç‚¹åœ¨å»ºç«‹åŽå°±ä¸å†æ”¹å˜ï¼Œè¿™ç§ç­–ç•¥æä¾›äº†â€œsession affinity”或“sticky sessions”。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:184
@@ -633,14 +649,14 @@
 "same target service. So if a particular client downloads two stubs for the "
 "same target service (e.g. an EJB), each stub will use the same target."
 msgstr ""
-"JBoss 3.2 里的新的负载平衡选项是 \"First AvailableIdenticalAllProxies"
-"\"  (<literal>org.jboss.ha.framework.interfaces."
-"FirstAvailableIdenticalAllProxies</literal>)。它与 \"First Available\" 有相同"
-"çš„è¡Œä¸ºï¼Œä½†é€‰å–çš„ç›®æ ‡èŠ‚ç‚¹ç”±æ‰€æœ‰åŒä¸€ \"family\" 的客户端拦截器共享。"
+"First AvailableIdentical All Proxies (<literal>org.jboss.ha.framework.interfaces."
+"FirstAvailableIdenticalAllProxies</literal>)：它与 \"First Available\" 有相同"
+"çš„è¡Œä¸ºï¼Œä½†é€‰å–çš„ç›®æ ‡èŠ‚ç‚¹ç”±æ‰€æœ‰å’Œç›¸åŒç›®æ ‡æœåŠ¡å…³è”çš„ç›¸åŒå®¢æˆ·ç«¯ VM 里的所有 stub å…±äº«ã€‚æ‰€ä»¥ï¼Œå¦‚æžœæŸä¸ªå®¢æˆ·ç«¯ä¸ºç›¸åŒçš„ç›®æ ‡æœåŠ¡ï¼ˆä¾‹å¦‚ EJB）下载了两个 stub，每个 stub éƒ½å°†ä½¿ç”¨ç›¸åŒçš„ç›®æ ‡ã€‚"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:190
 #, no-c-format
+#, fuzzy
 msgid ""
 "Each of the above is an implementation of the org.jboss.ha.framework."
 "interfaces.LoadBalancePolicy interface; users are free to write their own "
@@ -648,16 +664,19 @@
 "In later sections we'll see how to configure the load balance policies used "
 "by different services."
 msgstr ""
+"上面都是 org.jboss.ha.framework."
+"interfaces.LoadBalancePolicy æŽ¥å£çš„å®žçŽ°ã€‚ç”¨æˆ·å¯ä»¥æŒ‰ç…§éœ€è¦è‡ªç”±ç¼–å†™è‡ªå·±çš„å®žçŽ°ã€‚åœ¨åŽé¢çš„ç« èŠ‚é‡Œï¼Œæˆ‘ä»¬å°†çœ‹çœ‹å¦‚ä½•é…ç½®ä¸åŒæœåŠ¡ä½¿ç”¨çš„è´Ÿè½½å¹³è¡¡ç­–ç•¥ã€‚"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:194
 #, fuzzy, no-c-format
 msgid "External load balancer architecture"
-msgstr "The load balancer architecture for clustering"
+msgstr "外部负载平衡系统的架构"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:196
 #, no-c-format
+#, fuzzy
 msgid ""
 "As noted above, an external load balancer provides its own load balancing "
 "capabilities. What capabilities are supported depends on the provider of the "
@@ -666,17 +685,19 @@
 "enabled, once the load balancer routes a request from a client to node A and "
 "the server initiates a session, all future requests associated with that "
 "session must be routed to node A, so long as node A is available."
-msgstr ""
+msgstr "如上所述，外部的负载平衡系统提供自己的负载平衡能力。支持的功能取决于负载平衡系统的提供者。JBoss 对其唯一的要求是负载平衡系统必须支持“session affinitiy”（也称为“sticky sessions”）。启用了 session affinitiy 后，当负载平衡系统从客户请求路由到节点 A 时，服务器会初始化一个会话，只要节点 A 可用，将来和该会话关联的所有请求都必须转发给节点 A。"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:206
 #, no-c-format
+#, fuzzy
 msgid "Farming Deployment"
 msgstr "Farming 部署"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:207
 #, no-c-format
+#, fuzzy
 msgid ""
 "The easiest way to deploy an application into the cluster is to use the "
 "farming service. That is to hot-deploy the application archive file (e.g., "
@@ -690,11 +711,12 @@
 "cluster server nodes farm folder (triggers undeployment.) You should "
 "manually delete the application from the farm folder of any server node not "
 "currently connected to the cluster."
-msgstr ""
+msgstr "在群集里部署应用程序的最简单方法是使用 farming 服务。把应用程序归档文件（如 EAR、WAR 或 SAR）热部署到任何群集成员的 <code>all/farm/</code> ç›®å½•ä¸‹ï¼Œåº”ç”¨ç¨‹åºå°†è‡ªåŠ¨åœ°åœ¨æ‰€æœ‰èŠ‚ç‚¹é—´å¤åˆ¶ã€‚å¦‚æžœä¹‹åŽæœ‰èŠ‚ç‚¹åŠ å…¥ç¾¤é›†ï¼Œå®ƒå°†èŽ·å–æ‰€æœ‰ç”¨ farm éƒ¨ç½²çš„åº”ç”¨ç¨‹åºå¹¶åœ¨å¯åŠ¨æ—¶è¿›è¡Œæœ¬åœ°éƒ¨ç½²ã€‚å¦‚æžœä½ ä»Žç¾¤é›†æœåŠ¡å™¨èŠ‚ç‚¹çš„ <literal>farm/</literal> èŠ‚ç‚¹é‡Œåˆ é™¤åº”ç”¨ç¨‹åºï¼Œè¿™ä¸ªåº”ç”¨ç¨‹åºå°†åœ¨æœ¬åœ°å¸è½½å¹¶ä»Žå…¶ä»–èŠ‚ç‚¹çš„ farm ç›®å½•é‡Œåˆ é™¤ï¼ˆè§¦å‘å¸è½½ï¼‰ã€‚ä½ åº”è¯¥ä»Žä»»ä½•æœåŠ¡å™¨èŠ‚ç‚¹çš„ farm ç›®å½•ä¸‹æ‰‹å·¥åˆ é™¤ç›®å‰æœªè¿žæŽ¥ç¾¤é›†çš„åº”ç”¨ç¨‹åºã€‚"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:217
 #, no-c-format
+#, fuzzy
 msgid ""
 "Currently, due to an implementation weakness, the farm deployment service "
 "only works for 1) archives located in the farm/ directory of the first node "
@@ -705,22 +727,24 @@
 "the application really represents a new deployment or represents an old "
 "deployment that was removed from the rest of the cluster while the newly "
 "starting node was off-line. We are working to resolve this issue."
-msgstr ""
+msgstr "目前，由于程序上的缘故，farm 部署服务只能用于 1) ä½äºŽåŠ å…¥ç¾¤é›†çš„ç¬¬ä¸€ä¸ªèŠ‚ç‚¹çš„ farm 目录下的归档 或 2) 热部署的归档。如果首先把一个新程序放在 farm ç›®å½•ä¸‹ï¼Œç„¶è€Œå¯åŠ¨æœåŠ¡å™¨ä½¿å…¶åŠ å…¥çŽ°æœ‰çš„ç¾¤é›†ï¼Œè¿™ä¸ªåº”ç”¨ç¨‹åºä¸ä¼šåœ¨ç¾¤é›†é—´éƒ¨ç½²ã€‚è¿™æ˜¯å› ä¸º farm æœåŠ¡ä¸çŸ¥é“è¿™ä¸ªç¨‹åºæ˜¯å¦ç¡®å®žæ˜¯ä¸€ä¸ªæ–°éƒ¨ç½²è¿˜æ˜¯å½“æ–°å¯åŠ¨çš„èŠ‚ç‚¹ä¸‹çº¿æ—¶ä»Žç¾¤é›†é‡Œåˆ é™¤çš„æ—§éƒ¨ç½²ã€‚æˆ‘ä»¬æ­£åœ¨åŠªåŠ›è§£å†³è¿™ä¸ªé—®é¢˜ã€‚"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:220
 #, no-c-format
+#, fuzzy
 msgid ""
 "You can only put zipped archive files, not exploded directories, in the farm "
 "directory. If exploded directories are placed in farm the directory contents "
 "will be replicated around the cluster piecemeal, and it is very likely that "
 "remote nodes will begin trying to deploy things before all the pieces have "
 "arrived, leading to deployment failure."
-msgstr ""
+msgstr "ä½ å¯ä»¥åœ¨ farm 目录里只放入压缩的归档文件而不是扩展目录。如果在 farm 里放入了扩展的目录，其内容将在群集里逐渐进行复制，远程节点就很可能在所有的内容到达前试图部署，从而导致部署失败。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:223
 #, no-c-format
+#, fuzzy
 msgid ""
 "Farmed deployment is not atomic. A problem deploying, undeploying or "
 "redeploying an application on one node in the cluster will not prevent the "
@@ -729,7 +753,7 @@
 "quite likely, for example, that a redeployment will happen on all nodes in "
 "the cluster simultaneously, briefly leaving no nodes in the cluster "
 "providing service."
-msgstr ""
+msgstr "Farm 部署不是原子的。在一个节点上的部署、卸载、重部署出现问题并不会阻止在其他节点上的部署。它没有回滚能力。部署也不是交错的，在所有节点上的重部署很可能是同时进行的，使得群集里在短期没有节点可以提供服务。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:227
@@ -745,11 +769,10 @@
 "clustering enabled."
 msgstr ""
 "在 JBoss AS 发行版本里，Farming 在 <literal>all</literal> 配置里是缺省被启用"
-"çš„ï¼Œæ‰€ä»¥ä½ ä¸éœ€è¦è‡ªå·±æ¥è®¾ç½®å®ƒã€‚é…ç½®æ–‡ä»¶æ”¾åœ¨ <literal>deploy/deploy.last</"
-"literal> ç›®å½•ä¸‹ã€‚å¦‚æžœä½ æƒ³åœ¨è‡ªå®šä¹‰çš„é…ç½®æ–‡ä»¶é‡Œå¯ç”¨ farming，只需要建立如下所示"
-"的 XML 文件（<literal>farm-service.xml</literal>）并把它拷贝到 JBoss 的 "
+"çš„ï¼Œæ‰€ä»¥ä½ ä¸éœ€è¦è‡ªå·±æ¥è®¾ç½®å®ƒã€‚é…ç½®æ–‡ä»¶ <literal>farm-service.xml</"
+"literal> 放在 deploy/deploy.last ç›®å½•ä¸‹ã€‚å¦‚æžœä½ æƒ³åœ¨è‡ªå®šä¹‰çš„é…ç½®æ–‡ä»¶é‡Œå¯ç”¨ farming，只需要把 farm-service.xml</literal> 复制到 JBoss çš„ "
 "<literal>$JBOSS_HOME/server/your_own_config/deploy</literal> ç›®å½•ä¸‹ã€‚è¯·ç¡®ä¿ä½ "
-"的自定义配置文件启用了群集系统。"
+"的自定义配置文件启用了群集功能。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:229
@@ -758,8 +781,8 @@
 "After deploying farm-service.xml you are ready to rumble. The required "
 "FarmMemberService MBean attributes for configuring a farm are listed below."
 msgstr ""
-"在部署了 <literal>farm-service.xml</literal> 之后，下面所列是配置 farm 所需"
-"的 <literal>FarmMemberService</literal> MBean 属性。"
+"在部署了 farm-service.xml 之后，下面所列是配置 farm 所需"
+"的 FarmMemberService MBean 属性。"
 
 #. Tag: programlisting
 #: Clustering_Guide_Introduction.xml:232
@@ -791,11 +814,16 @@
 "            name=\"jboss:service=FarmMember,partition=DefaultPartition"
 "\"&gt;     \n"
 "        ...      \n"
-"        &lt;attribute name=\"PartitionName\"&gt;DefaultPartition&lt;/"
+"        \n"
+"        &lt;depends optional-attribute-name=\"ClusterPartition\" \n"
+"        proxy-type=\"attribute\"&gt;\n"
+"                jboss:service=${jboss.partition.name:DefaultPartition}\n"
+"                &lt;/depends&gt;     \n"
+"                &lt;attribute name=\"ScanPeriod\"&gt;5000&lt;/"
 "attribute&gt;      \n"
-"        &lt;attribute name=\"ScanPeriod\"&gt;5000&lt;/attribute&gt;      \n"
-"        &lt;attribute name=\"URLs\"&gt;farm/&lt;/attribute&gt;     \n"
-"    &lt;/mbean&gt;       \n"
+"                &lt;attribute name=\"URLs\"&gt;farm/&lt;/attribute&gt;     \n"
+"        ...\n"
+"        &lt;/mbean&gt;       \n"
 "&lt;/server&gt;"
 
 #. Tag: para
@@ -805,9 +833,7 @@
 "<emphasis role=\"bold\">ClusterPartition</emphasis> is a required attribute "
 "to inject the HAPartition service that the farm service uses for intra-"
 "cluster communication."
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis> 是用来指定节点名称的可选属"
-"性。它的缺省值是 <literal>DefaultPartition</literal>。"
+msgstr "<emphasis role=\"bold\">ClusterPartition</emphasis> 是注入 farm 服务用于群集内通信的 HAPartition 服务的必需属性。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:240
@@ -820,12 +846,13 @@
 "directory (e.g. <literal>$JBOSS_HOME/server/all/</literal>)."
 msgstr ""
 "<emphasis role=\"bold\">URLs</emphasis> 指向部署者（deployer）用来观察文件部"
-"署的目录。如果这个目录不存在，MBean 将创建它。而且，\".\" 指向配置目录（也就"
-"是：<literal>$JBOSS_HOME/server/all/</literal>）。"
+"署的目录。如果这个目录不存在，MBean 将创建它。如果没有提供完整的 URL，它指向相对配置目录（也就"
+"是：<literal>$JBOSS_HOME/server/all/</literal>）的路径。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:245
 #, no-c-format
+#, fuzzy
 msgid ""
 "<emphasis role=\"bold\">ScanPeriod</emphasis> specifies the interval at "
 "which the folder must be scanned for changes.. Its default value is "
@@ -851,11 +878,12 @@
 "用 <literal>FarmMemberService</literal> MBean 里的 "
 "<literal>URLDeploymentScanner</literal> MBean 定义的所有属性。实际上，上列 "
 "<literal>URLs</literal> 和 <literal>ScanPeriod</literal> 属性都是从 "
-"<literal>URLDeploymentScanner</literal> MBean 继承过来的。"
+"<literal>URLDeploymentScanner</literal> MBean 继承过来的。 "
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:258
 #, no-c-format
+#, fuzzy
 msgid "Distributed state replication services"
 msgstr "分布式状态复制服务"
 
@@ -880,7 +908,7 @@
 "同的会话状态，而不用管是哪个节点处理请求。在 entity bean 应用程序里，bean 对"
 "象有时候需要跨群集地缓存来减少数据库负载。目前，JBoss AS 里的状态复制（state "
 "replication）和分布式缓存服务（distributed cache service）由两个途径提供："
-"<literal>HASessionState</literal> MBean 和 JBoss Cache framework。"
+"<literal>HASessionState</literal> MBean 和 JBoss Cache 框架。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:266
@@ -892,7 +920,7 @@
 "cluster-service.xml</literal> file. We will show its configuration options "
 "in the EJB 2.x stateful session bean section later."
 msgstr ""
-"<literal>HASessionState</literal> MBean 为 EJB 2.x 的 stateful session beans "
+"<literal>HASessionState</literal> MBean 是一个旧的服务，它为 EJB 2.x 的 stateful session beans "
 "和 JBoss 3.x 和  4.x 里的 HTTP 负载平衡提供会话复制（session replication）和"
 "分布式缓存服务（distributed cache service）。<literal>all/deploy/cluster-"
 "service.xml</literal> 文件里定义了这个 MBean。我们会在后面的 EJB 2.x "
@@ -901,16 +929,18 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:269
 #, no-c-format
+#, fuzzy
 msgid ""
 "The <literal>DistributedState</literal> Mbean is a legacy service built on "
 "the HAPartition service. It is supported for backwards compatibility "
 "reasons, but new applications should not use it; they should use the much "
 "more sophisticated JBoss Cache instead."
-msgstr ""
+msgstr "<literal>DistributedState</literal> Mbean 是一个构建在 HAPartition 服务上的旧服务。支持它是为了向后兼容，但新程序不应该使用它而应该使用更为复杂的 JBoss Cache。"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:275
 #, no-c-format
+#, fuzzy
 msgid ""
 "As mentioned above JBoss Cache is used to provide cache services for HTTP "
 "sessions, EJB 3.0 session beans and EJB 3.0 entity beans. It is the primary "
@@ -918,7 +948,7 @@
 "for any custom caching requirements your applications may have. We will "
 "cover JBoss Cache in more detail when we discuss specific services in the "
 "next several sections.."
-msgstr ""
+msgstr "如上所述，JBoss Cache 为 HTTP 会话、EJB 3.0 session bean å’Œ EJB 3.0 entity bean 提供缓存服务。它是 JBoss AS é‡Œä¸»è¦çš„åˆ†å¸ƒå¼çŠ¶æ€ç®¡ç†å·¥å…·ï¼Œè€Œä¸”å¯¹äºŽä»»ä½•è‡ªå®šä¹‰ç¼“å­˜éœ€æ±‚æ¥è¯´éƒ½æ˜¯ä¸é”™çš„é€‰æ‹©ã€‚åœ¨åŽé¢ç« èŠ‚é‡Œè®¨è®ºç‰¹æ®ŠæœåŠ¡æ—¶ï¼Œæˆ‘ä»¬å°†ä»‹ç» JBoss Cache 的更多细节。"
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:286
@@ -1361,10 +1391,8 @@
 #. Tag: programlisting
 #: Clustering_Guide_Introduction.xml:468
 #, no-c-format
-msgid ""
-"java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100"
-msgstr ""
-"java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100"
+msgid "java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100"
+msgstr "java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:469
@@ -1592,9 +1620,7 @@
 "<emphasis role=\"bold\">Cluster Partition</emphasis> is a required attribute "
 "to inject the HAPartition service that HA-JNDI uses for intra-cluster "
 "communication."
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis> 是用来指定节点名称的可选属"
-"性。它的缺省值是 <literal>DefaultPartition</literal>。"
+msgstr "<emphasis role=\"bold\"></emphasis> HAPartition."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:536
@@ -1913,17 +1939,14 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:604
 #, no-c-format
+#, fuzzy
 msgid ""
 "Clustering stateless session beans is most probably the easiest case: as no "
 "state is involved, calls can be load-balanced on any participating node (i."
 "e. any node that has this specific bean deployed) of the cluster. To make a "
 "bean clustered, you need to modify its <literal>jboss.xml</literal> "
 "descriptor to contain a <literal>&lt;clustered&gt;</literal> tag."
-msgstr ""
-"群集的 stateless session beans æœ‰å¯èƒ½æ˜¯æœ€ç®€å•çš„ï¼šå› ä¸ºä¸æ¶‰åŠåˆ°çŠ¶æ€ï¼Œè°ƒç”¨å¯ä»¥åœ¨"
-"群集里的任何节点（部署有这个 bean 的节点）上进行负载平衡。要群集一个 beanï¼Œä½ "
-"需要修改它的 <literal>jboss.xml</literal> 描述符，使它包含一个 <literal>&lt;"
-"clustered&gt;</literal> æ ‡ç­¾ã€‚"
+msgstr "群集<literal></literal><literal>&lt;&gt;</literal>."
 
 #. Tag: programlisting
 #: Clustering_Guide_Introduction.xml:608
@@ -2054,6 +2077,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:642
 #, no-c-format
+#, fuzzy
 msgid ""
 "Clustering stateful session beans is more complex than clustering their "
 "stateless counterparts since JBoss needs to manage the state information. "
@@ -2063,13 +2087,7 @@
 "states for clustered EJB 2.x stateful session beans. In this section, we "
 "cover both the session bean configuration and the <literal>HASessionState</"
 "literal> MBean configuration."
-msgstr ""
-"既然 JBoss 需要管理状态信息，群集 stateful session beans 就比群集 stateles "
-"ssession beans 更为复杂。当 stateful session beans 的状态改变时，所有状态在群"
-"集中复制和同步。JBoss AS 使用 <literal>HASessionState</literal> MBean 来为群"
-"集的 EJB 2.x stateful session beans 管理分布式的会话状态。在这部分内容里，我"
-"们将介绍 session bean 的配置和 <literal>HASessionState</literal> MBean 的配"
-"置。"
+msgstr "群集<literal></literal><literal></literal>."
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:649
@@ -2292,22 +2310,18 @@
 "<emphasis role=\"bold\">ClusterPartition</emphasis> is a required attribute "
 "to inject the HAPartition service that HA-JNDI uses for intra-cluster "
 "communication."
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis> 是用来指定节点名称的可选属"
-"性。它的缺省值是 <literal>DefaultPartition</literal>。"
+msgstr "<emphasis role=\"bold\"></emphasis> HAPartition."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:690
 #, no-c-format
+#, fuzzy
 msgid ""
 "<emphasis role=\"bold\">JndiName</emphasis> is an optional attribute to "
 "specify the JNDI name under which this <literal>HASessionState</literal> "
 "service is bound. The default value is <literal>/HAPartition/Default</"
 "literal>."
-msgstr ""
-"<emphasis role=\"bold\">JndiName</emphasis> 是一个可选属性，它指定这个 "
-"<literal>HASessionState</literal> 服务被绑定的 JNDI 名。它的缺省值是 "
-"<literal>/HAPartition/Default</literal>。"
+msgstr "<emphasis role=\"bold\"></emphasis><literal></literal><literal> HAPartition</literal>."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:696
@@ -3728,15 +3742,13 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:986
 #, no-c-format
-msgid ""
-"First, in persistence.xml you need to tell Hibernate to enable query caching:"
+msgid "First, in persistence.xml you need to tell Hibernate to enable query caching:"
 msgstr ""
 
 #. Tag: screen
 #: Clustering_Guide_Introduction.xml:989
 #, no-c-format
-msgid ""
-"&lt;property name=\"hibernate.cache.use_query_cache\" value=\"true\"/&gt;"
+msgid "&lt;property name=\"hibernate.cache.use_query_cache\" value=\"true\"/&gt;"
 msgstr ""
 
 #. Tag: para
@@ -4088,8 +4100,7 @@
 msgid ""
 "Next, create a new file named <literal>APACHE_HOME/conf/mod-jk.conf</"
 "literal>:"
-msgstr ""
-"然后，建立一个叫 <literal>APACHE_HOME/conf/mod-jk.conf</literal> 的文件。"
+msgstr "然后，建立一个叫 <literal>APACHE_HOME/conf/mod-jk.conf</literal> 的文件。"
 
 #. Tag: programlisting
 #: Clustering_Guide_Introduction.xml:1090
@@ -4738,13 +4749,14 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1204
 #, no-c-format
+#, fuzzy
 msgid ""
 "Note that the value of the mbean element's code attribute is org.jboss.cache."
 "aop.TreeCacheAop, which is different from the other JBoss Cache Mbeans used "
 "in JBoss AS. This is because FIELD granularity HTTP session replication "
 "(covered below) needs the added features of the <literal>TreeCacheAop</"
 "literal> (a.k.a. <literal>PojoCache</literal>) class."
-msgstr ""
+msgstr "备注 <literal></literal><literal></literal>."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1207
@@ -5015,13 +5027,7 @@
 "without being replicated, as a safeguard its timestamp will be replicated no "
 "matter what. So, ACCESS is only useful in special circumstances where the "
 "above safeguard is considered inadequate."
-msgstr ""
-"<emphasis role=\"bold\">ACCESS</emphasis>：这个选项表示：只要会话被访问，就把"
-"ä¼šè¯æ ‡è®°ä¸º ditryã€‚å› ä¸ºåœ¨æ¯ä¸ª HTTP 请求的过程中，会话都会被访问，所以会话每次"
-"都会被复制。会话实例里的时间戳也会相应地更新。由于复制并没有包括时间戳，其他"
-"群集节点的时间戳可能不会被更新。如果 HTTP 请求没有取出或修改任何会话属性，其"
-"他节点的会话就可能会先于活动节点过期。当设置了这个选项，会话的时间戳将在所有"
-"群集节点中同步。注意采用这个选项对性能影响很大，需要小心行事。"
+msgstr "<emphasis role=\"bold\"></emphasis> 备注 ."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1269
@@ -5557,6 +5563,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1399
 #, no-c-format
+#, fuzzy
 msgid ""
 "The JBoss Application Server (AS) provides support for a number of "
 "strategies for helping you deploy clustered singleton services. In this "
@@ -5566,7 +5573,7 @@
 "different nodes in the cluster start and stop; based on those notifications "
 "each node in the cluster can independently (but consistently) determine if "
 "it is now the master node and needs to begin providing a service."
-msgstr ""
+msgstr "HAPartition<literal> HAPartition</literal>."
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:1404
@@ -5608,8 +5615,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1411
 #, no-c-format
-msgid ""
-"Using deploy-hasingleton is very simple, but it does have two drawbacks:"
+msgid "Using deploy-hasingleton is very simple, but it does have two drawbacks:"
 msgstr ""
 
 #. Tag: para
@@ -5641,6 +5647,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1433
 #, no-c-format
+#, fuzzy
 msgid ""
 "If your service is an Mbean (i.e., not a J2EE deployment like an ear or war "
 "or jar), you can deploy it along with a service called an "
@@ -5651,7 +5658,7 @@
 "on your service telling it to begin providing service. If it determines it "
 "is no longer the master node, it invokes a method on your service telling it "
 "to stop providing service. Let's walk through an illustration."
-msgstr ""
+msgstr "HAPartition."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1436
@@ -5707,6 +5714,7 @@
 #. Tag: programlisting
 #: Clustering_Guide_Introduction.xml:1447
 #, no-c-format
+#, fuzzy
 msgid ""
 "<![CDATA[\n"
 " <server> \n"
@@ -5737,6 +5745,27 @@
 "         </mbean> \n"
 "</server> ]]>"
 msgstr ""
+"\n"
+"<server>\n"
+"\n"
+"<mbean code=\"org.jboss.ha.examples.HASingletonExample\" \n name=“jboss:service=HASingletonExample\"/>\n"
+"\n"
+"\n"
+"<mbean code=\"org.jboss.ha.singleton.HASingletonController\" \n name=\"jboss:service=ExampleHASingletonController\">\n"
+"\n"
+" HAPartition\n"
+"<depends optional-attribute-name=\"ClusterPartition\" proxy-type=\"attribute\">\n"
+"\n"
+"</depends>\n"
+"\n"
+"<depends optional-attribute-name=\"TargetName\">\n"
+"\n"
+"</depends>\n"
+"\n"
+"<attribute name=\"TargetStartMethod\"></attribute>\n"
+"<attribute name=\"TargetStopMethod\"></attribute>\n"
+"</mbean>\n"
+"</server>"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1449
@@ -5914,6 +5943,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1500
 #, no-c-format
+#, fuzzy
 msgid ""
 "Prior to JBoss AS 4.2.0, the methodology for this was fixed and simple. For "
 "each member of the cluster, the HAPartition mbean maintains an attribute "
@@ -5924,7 +5954,7 @@
 "CurrentView attribute in the <literal>jboss:service=DefaultPartition</"
 "literal> mbean. Every member of the cluster will have the same view, with "
 "the members in the same order."
-msgstr ""
+msgstr "HAPartition<literal></literal>."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1503
@@ -5940,6 +5970,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1506
 #, no-c-format
+#, fuzzy
 msgid ""
 "To further our example, let's say there is a singleton service (i.e., an "
 "<literal>HASingletonController</literal>) named Foo that's deployed around "
@@ -5948,11 +5979,12 @@
 "are deployed where, in view order. So, on every node in the cluster, the "
 "<literal>HAPartition</literal> service knows that the view with respect to "
 "the Foo service is {A, C, D} (no B)."
-msgstr ""
+msgstr "<literal></literal><literal> HAPartition</literal><literal> HAPartition</literal>."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1510
 #, no-c-format
+#, fuzzy
 msgid ""
 "Whenever there is a change in the cluster topology of the Foo service, the "
 "<literal>HAPartition</literal> service invokes a callback on Foo notifying "
@@ -5962,7 +5994,7 @@
 "independently decide if it is now the master. The Foo service on each node "
 "does this by checking if they are the first member of the view – if they "
 "are, they are the master; if not, they're not. Simple as that."
-msgstr ""
+msgstr "<literal> HAPartition</literal>."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1514
@@ -6812,8 +6844,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1774
 #, 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
@@ -7058,8 +7089,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1867
 #, 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
@@ -7268,8 +7298,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_Introduction.xml:1943
@@ -7360,8 +7389,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1974
 #, no-c-format
-msgid ""
-"Here is another example PING configuration for contacting a Gossip Router."
+msgid "Here is another example PING configuration for contacting a Gossip Router."
 msgstr ""
 
 #. Tag: programlisting
@@ -7393,8 +7421,7 @@
 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> 指定等待应答的最长时间（毫秒数）"
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:1988
@@ -8024,6 +8051,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:2289
 #, no-c-format
+#, fuzzy
 msgid ""
 "This suspects a member when the socket to the neighbor has been closed "
 "abonormally (e.g. process crash, because the OS closes all sockets). "
@@ -8032,7 +8060,7 @@
 "seconds. Note that with this example, if you have your system stopped in a "
 "breakpoint in the debugger, the node you're debugging will be suspected "
 "after ca 50 seconds."
-msgstr ""
+msgstr "备注 ."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:2292
@@ -8523,8 +8551,7 @@
 #. Tag: programlisting
 #: Clustering_Guide_Introduction.xml:2495
 #, fuzzy, no-c-format
-msgid ""
-"&lt;pbcast.STATE_TRANSFER down_thread=\"false\" up_thread=\"false\"/&gt;"
+msgid "&lt;pbcast.STATE_TRANSFER down_thread=\"false\" up_thread=\"false\"/&gt;"
 msgstr ""
 "&lt;pbcast.STATE_TRANSFER \n"
 "    down_thread=\"false\"\n"
@@ -8744,8 +8771,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:2574
 #, 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
@@ -8818,13 +8844,14 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:2617
 #, no-c-format
+#, fuzzy
 msgid ""
 "Within JBoss AS, there are a number of services that independently create "
 "JGroups channels -- 3 different JBoss Cache services (used for HttpSession "
 "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 "HAPartition."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:2620
@@ -8859,13 +8886,14 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:2629
 #, no-c-format
+#, fuzzy
 msgid ""
 "For example, say we have a production cluster of 3 machines, each of which "
 "has an HAPartition deployed along with a JBoss Cache used for web session "
 "clustering. The HAPartition channels should not communicate with the JBoss "
 "Cache channels. They should use a different group name and multicast port. "
 "They can use the same multicast address, although they don't need to."
-msgstr ""
+msgstr "HAPartition HAPartition."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:2632
@@ -8879,13 +8907,14 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:2635
 #, no-c-format
+#, fuzzy
 msgid ""
 "For example, say we have a production cluster of 3 machines, each of which "
 "has an HAPartition deployed. On the same network there is also a QA cluster "
 "of 3 machines, which also has an HAPartition deployed. The HAPartition group "
 "name, multicast address, and multicast port for the production machines must "
 "be different from those used on the QA machines."
-msgstr ""
+msgstr "HAPartition HAPartition HAPartition."
 
 #. Tag: title
 #: Clustering_Guide_Introduction.xml:2641
@@ -8896,6 +8925,7 @@
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:2642
 #, no-c-format
+#, fuzzy
 msgid ""
 "The group name for a JGroups channel is configured via the service that "
 "starts the channel. Unfortunately, different services use different "
@@ -8903,11 +8933,12 @@
 "configured in the deploy/cluster-service.xml file, this is configured via a "
 "PartitionName attribute. For JBoss Cache services, the name of the attribute "
 "is ClusterName."
-msgstr ""
+msgstr "HAPartition."
 
 #. Tag: para
 #: Clustering_Guide_Introduction.xml:2645
 #, no-c-format
+#, fuzzy
 msgid ""
 "Starting with JBoss AS 4.0.4, for the HAPartition and all the standard JBoss "
 "Cache services, we make it easy for you to create unique groups names simply "
@@ -8916,7 +8947,7 @@
 "jboss.partition.name system property, which is used as a component in the "
 "configuration of the group name in all the standard clustering configuration "
 "files. For example,"
-msgstr ""
+msgstr "HAPartition<screen></screen>"
 
 #. Tag: screen
 #: Clustering_Guide_Introduction.xml:2649
@@ -9131,3 +9162,4 @@
 "will not process any other messages, including heartbeats, and therefore B "
 "will not receive the heartbeat ack and will suspect C."
 msgstr ""
+