[jboss-cvs] JBossAS SVN: r83346 - 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
Fri Jan 23 01:20:54 EST 2009
Author: xhuang at jboss.com
Date: 2009-01-23 01:20:54 -0500 (Fri, 23 Jan 2009)
New Revision: 83346
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_HTTP.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_HTTP.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_HTTP.po 2009-01-23 06:19:35 UTC (rev 83345)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_HTTP.po 2009-01-23 06:20:54 UTC (rev 83346)
@@ -1,18 +1,20 @@
+# translation of Clustering_Guide_HTTP.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.
#
msgid ""
msgstr ""
-"Project-Id-Version: JBEAP 420\n"
+"Project-Id-Version: Clustering_Guide_HTTP\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-23 16:20+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"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: Clustering_Guide_HTTP.xml:5
@@ -41,13 +43,13 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:14
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Load-balancing of incoming invocations"
-msgstr "传入调用（incoming invocations）的负载平衡"
+msgstr "传入调用（incoming invocations）的负载平衡 "
#. Tag: para
#: Clustering_Guide_HTTP.xml:17
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"State replication is directly handled by JBoss. When you run JBoss in the "
"<literal>all</literal> configuration, session state replication is enabled "
@@ -56,12 +58,12 @@
"is automtically replicated across all JBoss instances in the cluster."
msgstr ""
"状态复制（State replication）由 JBoss 直接处理。当你在 <literal>all</"
-"literal> 配置里运行 JBoss，会话状态复制缺省是启用的。只要部署了你的 web 应用"
+"literal> 配置里运行 JBoss，会话状态复制缺省是启用的。只要在 <filename>web.xml</filename>（如下所示）配置并部署了你的 web 应用"
"程序，它的会话状态就已经复制在群集里的所有 JBoss 实例中了。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:19
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"However, load-balancing is a different story; it is not handled by JBoss "
"itself and requires an external load balancer. aThis function could be "
@@ -70,19 +72,18 @@
"common scenario, we will demonstrate how to set up a software load balancer "
"using Apache httpd and mod_jk."
msgstr ""
-"然而，负载平衡是不一样的。它不是由 JBoss 自己处理的，它需要额外的软件。我们将"
-"演示怎样设立 Apache 和 mod_jk，这是一个很常见的例子。但这需要专门的硬件开关，"
-"路由器（如 Cisco LoadDirector）或其他专门的软件来执行。"
+"然而，负载平衡是不一样的。它不是由 JBoss 自己处理的，它需要外部的软件。这样的功能可以由专门的硬件开关或路由器（如 Cisco LoadDirector）或其他专门的软件来提供。我们将"
+"演示怎样设立常见的使用 Apache 和 mod_jk 的软件负载平衡系统。"
#. Tag: title
#: Clustering_Guide_HTTP.xml:22
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Note"
msgstr "备注"
#. Tag: para
#: Clustering_Guide_HTTP.xml:24
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"A load-balancer tracks HTTP requests and, depending on the session to which "
"the request is linked, it dispatches the request to the appropriate node. "
@@ -110,13 +111,13 @@
#. Tag: title
#: Clustering_Guide_HTTP.xml:26
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Configuring load balancing using Apache and mod_jk"
-msgstr "配置 Apache 来装载 mod_jk"
+msgstr "用 Apache 和 mod_jk 来配置负载平衡系统"
#. Tag: para
#: Clustering_Guide_HTTP.xml:28
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Apache is a well-known web server which can be extended by plugging in "
"modules. One of these modules, mod_jk has been specifically designed to "
@@ -125,10 +126,8 @@
"containers while maintaining sticky sessions, which is what is most "
"interesting for us in this section."
msgstr ""
-"Apache 是一个很有名的 web 服务器，它可以通过插件来扩展。mod_jk（和最新的 "
-"mod_jk2）已经被特别的设计成可以允许从 Apache 转发请求到 Servlet 容器里。而"
-"且，当维护 sticky sessions 时，它也能够对 Servlet 容器的 HTTP 调用的负载进行"
-"平衡，这正是让我们感兴趣的地方。"
+"Apache 是一个很有名的 web 服务器，它可以通过插件来扩展。mod_jk 已经被特别的设计成可以允许从 Apache 转发请求到 Servlet 容器里。而且，当维护 sticky sessions 时，它也能够对 Servlet 容器的 HTTP 调用的负载进行"
+"平衡，这正是让我们最感兴趣的地方。"
#. Tag: title
#: Clustering_Guide_HTTP.xml:33
@@ -201,8 +200,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_HTTP.xml:51
@@ -402,7 +400,7 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:82
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Next, you need to configure mod_jk workers file <literal>conf/workers."
"properties</literal>. This file specifies where the different Servlet "
@@ -414,7 +412,7 @@
"然后，你需要配置 mod_jk 的 workers 文件 <literal>conf/workers.properties</"
"literal>。这个文件指定不同的 Servlet 容器的存放位置和怎样对它们之间的调用进行"
"负载平衡。这个配置文件包含了一个全局设置部分以及针对每个目标 Servlet 容器的设"
-"置部分。对于两个节点的设立，这个文件如下所示："
+"置部分。对于两个节点的设立，这个文件如下所示： "
#. Tag: programlisting
#: Clustering_Guide_HTTP.xml:87
@@ -492,7 +490,7 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:91
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"In the <literal>works.properties</literal> file, each node is defined using "
"the <literal>worker.XXX</literal> naming convention where <literal>XXX</"
@@ -504,11 +502,11 @@
"在 <literal>works.properties</literal> 文件里，每个节点都用 <literal>worker."
"XXX</literal> 命名规则命名，<literal>XXX</literal> 代表你给其中一个目标 "
"Servlet 容器选取的任意名字。对于每一个 worker，你必须给出在 Servlet 容器运行"
-"的 AJP13 connector 的主机名（或 IP 地址）和端口号。"
+"的 AJP13 connector 的主机名（或 IP 地址）和端口号。 "
#. Tag: para
#: Clustering_Guide_HTTP.xml:96
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>lbfactor</literal> attribute is the load-balancing factor for "
"this specific worker. It is used to define the priority (or weight) a node "
@@ -519,7 +517,7 @@
msgstr ""
"<literal>lbfactor</literal> 属性是对于特定的 worker 的负载平衡因子。它用来定"
"义一个节点对于其他节点的优先级（或权重）。这个数字越大，就要接收越多的 HTTP "
-"请求。这个设置可以用来调节不同服务器的处理能力。"
+"请求。这个设置可以用来调节不同服务器的处理能力。 "
#. Tag: para
#: Clustering_Guide_HTTP.xml:98
@@ -556,7 +554,7 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:108
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>sticky_session</literal> property specifies the cluster "
"behavior for HTTP sessions. If you specify <literal>worker.loadbalancer."
@@ -571,28 +569,25 @@
msgstr ""
"<literal>sticky_session</literal> 属性指定 HTTP 会话的群集系统行为。如果你指"
"定 <literal>worker.loadbalancer.sticky_session=0</literal>，每个请求会在节点 "
-"1 和节点 2 之间进行负载平衡。但是当用户在服务器上开始一个会话，把这个的用户的"
-"请求转发到同一服务器会是个好主意。这被称作 \"sticky session\"，因为客户总是使"
-"用处理他第一个请求的服务器。否则用户的会话数据就必须在两个服务器之间同步（即"
-"会话复制，请参考 <xref linkend=\"clustering-http-state\"/>）。为了启用 "
+"1 和节点 2 之间进行负载平衡。但是当用户在某个服务器上开始一个会话，把这个的用户的"
+"请求转发到同一服务器会是必要的，只要该服务器是可用的。这被称作 \"sticky session\"，因为客户总是使"
+"用处理他第一个请求的服务器。为了启用 "
"session stickiness，你需要把 <literal>worker.loadbalancer.sticky_session</"
"literal> 设置为 1。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:113
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"A non-loadbalanced setup with a single node requires a <literal>worker."
"list=node1</literal> entry."
-msgstr ""
-"单节点的非负载平衡的设立需要设置 <literal>worker.list=node1</literal> 条目，"
-"才能使 mod_jk 正常工作。"
+msgstr "单节点的非负载平衡的设立需要设置 <literal>worker.list=node1</literal> 条目。"
#. Tag: title
#: Clustering_Guide_HTTP.xml:118
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Configuring JBoss to work with mod_jk"
-msgstr "配置 mod_jk 里的 worker 节点"
+msgstr "配置 JBoss 里的 mod_jk"
#. Tag: para
#: Clustering_Guide_HTTP.xml:119
@@ -602,11 +597,11 @@
"so that they can expect requests forwarded from the mod_jk loadbalancer."
msgstr ""
"最后，我们必须在所有群集节点上配置 JBoss Tomcat 实例，它们才能接收从 mod_jk "
-"负载平衡系统转发的请求。"
+"负载平衡系统转发的请求。 "
#. Tag: para
#: Clustering_Guide_HTTP.xml:121
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"On each clustered JBoss node, we have to name the node according to the name "
"specified in <literal>workers.properties</literal>. For instance, on JBoss "
@@ -616,8 +611,8 @@
"literal> element and add an attribute <literal>jvmRoute</literal>:"
msgstr ""
"在每个群集节点上，我们得按 <literal>workers.properties</literal> 里指定的名字"
-"来命名节点名。例如，在 JBoss 实例节点1上，编辑 <literal>JBOSS_HOME/server/"
-"all/deploy/jbossweb-tomcat50.sar/server.xml</literal> 文件（有必要的话用你自"
+"来命名节点名。例如，在 JBoss 实例节点1上，编辑 <literal>JBOSS_HOME/server/all/deploy/jboss-web."
+"deployer/server.xml</literal> 文件（有必要的话用你自"
"己的服务器名代替<literal>/all</literal>）。定位 <literal><Engine></"
"literal> 元素并加入一个 <literal>jvmRoute</literal> 属性："
@@ -641,7 +636,7 @@
msgid ""
"You also need to be sure the AJP connector in server.xml is enabled (i.e., "
"uncommented). It is enabled by default."
-msgstr ""
+msgstr "你也需要确保启用了 server.xml 里的 AJP 连接器（也就是取消注释）。缺省它是被启用的。"
#. Tag: programlisting
#: Clustering_Guide_HTTP.xml:129
@@ -654,10 +649,16 @@
"emptySessionPath=\"true\" enableLookups=\"false\" redirectPort=\"8443\" /> ]]"
">"
msgstr ""
+"<![CDATA[ \n"
+"<!-- Define an AJP 1.3 Connector on port 8009 --> \n"
+"<Connector port=\"8009\" address=\"${jboss.bind.address}\" protocol=\"AJP/1.3"
+"\" \n"
+"emptySessionPath=\"true\" enableLookups=\"false\" redirectPort=\"8443\" /> ]]"
+">"
#. Tag: para
#: Clustering_Guide_HTTP.xml:131
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Then, for each JBoss Tomcat instance in the cluster, we need to tell it that "
"mod_jk is in use, so it can properly manage the <literal>jvmRoute</literal> "
@@ -668,8 +669,7 @@
"literal> element with a name of <literal>UseJK</literal>, and set its value "
"to <literal>true</literal>:"
msgstr ""
-"然后，对群集里的每个 JBoss Tomcat 实例，我们需要使它们在它们的会话 cookies 里"
-"加入 <literal>jvmRoute</literal> 值，这样 mod_jk 才能指引进来的请求。编辑 "
+"然后，对群集里的每个 JBoss Tomcat 实例，我们需要通知它 mod_jk 正在使用中，这样它就可以正确管理会话 cookies 里后的 <literal>jvmRoute</literal> 值，这样 mod_jk 才能正确路由转入的请求。编辑 "
"<literal>JBOSS_HOME/server/all/deploy/jbossweb-tomcat50.sar/META-INF/jboss-"
"service.xml</literal> 文件（有必要的话用你自己的服务器名代替 <literal>/all</"
"literal>）。用 <literal>UseJK</literal>名来定位<literal><attribute></"
@@ -708,9 +708,9 @@
#. Tag: title
#: Clustering_Guide_HTTP.xml:149
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Configuring HTTP session state replication"
-msgstr "配置 HTTP 会话状态复制（session state replication）"
+msgstr "配置 HTTP 会话状态复制（state replication）"
#. Tag: para
#: Clustering_Guide_HTTP.xml:150
@@ -719,11 +719,11 @@
"The preceding discussion has been focused on using mod_jk as a load "
"balancer. The content of the remainder our discussion of clustering HTTP "
"services in JBoss AS applies no matter what load balancer is used."
-msgstr ""
+msgstr "前面的讨论集中于把 mod_jk 作为负载平衡系统使用。而不管使用了哪个负载平衡系统，后面关于群集 HTTP 服务的内容都适用。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:153
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"In <xref linkend=\"clustering-http-nodes\"/>, we covered how to use sticky "
"sessions to make sure that a client in a session always hits the same server "
@@ -741,7 +741,7 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:155
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>jboss.cache:service=TomcatClusteringCache</literal> MBean makes "
"use of JBoss Cache to provide HTTP session replication services to the JBoss "
@@ -750,37 +750,37 @@
msgstr ""
"<literal>jboss.cache:service=TomcatClusteringCache</literal> MBean 利用 "
"JBoss Cache 来为 JBoss Tomcat 群集里的 HTTP 负载平衡系统提供 HTTP 会话复制服"
-"务。<literal>deploy/tc5-cluster.sar/META-INF/jboss-service.xml</literal> 文件"
+"务。<literal>deploy/jboss-web-"
+"cluster.sar/META-INF/jboss-service.xml file</literal> 文件"
"里定义了这个 MBean。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:158
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Before AS 4.2.0, the location of the HTTP session cache configuration file "
"was <literal>deploy/tc5-cluster.sar/META-INF/jboss-service.xml</literal>. "
"Prior to AS 4.0.4 CR2, the file was named <literal>deploy/tc5-cluster-"
"service.xml</literal>."
msgstr ""
-"在 AS 4.0.4 CR2 之前， HTTP 会话缓存配置文件是 <literal>deploy/tc5-cluster-"
-"service.xml</literal>。请参考 AS 4.0.3 文档来获得更多细节。"
+"在 AS 4.2.0 之前，HTTP 会话缓存配置文件是 <literal>deploy/tc5-cluster.sar/META-INF/jboss-service.xml</literal>。在 AS 4.0.4 CR2 之前，这个文件的名字是 <literal>deploy/tc5-cluster-"
+"service.xml</literal>。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:160
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Below is a typical <literal>deploy/jbossweb-cluster.sar/META-INF/jboss-"
"service.xml</literal> file. The configuration attributes in the "
"<literal>TomcatClusteringCache</literal> MBean are very similar to those in "
"the JBoss AS cache configuration."
msgstr ""
-"下面是一个典型的 <literal>deploy/tc5-cluster.sar/META-INF/jboss-service.xml</"
-"literal> 文件。<literal>TomcatClusteringCache</literal> MBean 里的配置属性和 "
-"<xref linkend=\"jbosscache-cache\"/> 里的非常相似。"
+"下面是一个典型的 <literal>deploy/jbossweb-cluster.sar/META-INF/jboss-"
+"service.xml</literal> 文件。<literal>TomcatClusteringCache</literal> MBean 里的配置属性和 JBoss AS cache 里的非常相似。"
#. Tag: programlisting
#: Clustering_Guide_HTTP.xml:163
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<mbean code=\"org.jboss.cache.aop.TreeCacheAop\"\n"
" name=\"jboss.cache:service=TomcatClusteringCache\">\n"
@@ -844,8 +844,10 @@
" ... ...\n"
" </attribute>\n"
" \n"
+" \n"
" <attribute name=\"LockAcquisitionTimeout\">15000</"
"attribute>\n"
+" <attribute name=\"SyncReplTimeout\">20000</attribute>\n"
"</mbean>"
#. Tag: para
@@ -858,23 +860,25 @@
"(covered below) needs the added features of the <literal>TreeCacheAop</"
"literal> (a.k.a. <literal>PojoCache</literal>) class."
msgstr ""
+"请注意，这个 MBean 的 code 属性值是 org.jboss.cache."
+"aop.TreeCacheAop，和其他 JBoss Cache Mbean 不同。这是因为字段级别的 HTTP 会话复制需要 <literal>TreeCacheAop</"
+"literal> 类的附加功能（也称为 <literal>PojoCache</literal>）"
#. Tag: para
#: Clustering_Guide_HTTP.xml:168
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The details of all the configuration options for a TreeCache MBean are "
"covered in the JBoss Cache documentation. Below, we will just discuss "
"several attributes that are most relevant to the HTTP cluster session "
"replication."
msgstr ""
-"<xref linkend=\"jbosscache-cache\"/> 里包括了 <literal>TreeCache</literal> "
-"MBean 的详细配置。下面，我们将讨论和 HTTP 群集会话复制（cluster session "
+"JBoss Cache 文档里包括了 TreeCache MBean 的详细配置。下面，我们将讨论和 HTTP 群集会话复制（cluster session "
"replication）最为相关的几个属性。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:171
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">TransactionManagerLookupClass</emphasis> sets the "
"transaction manager factory. The default value is <literal>org.jboss.cache."
@@ -882,9 +886,8 @@
"participate in JTA-specific transactions. Instead, the cache manages its own "
"transactions. Please do not change this."
msgstr ""
-"<emphasis role=\"bold\">TransactionManagerLookupClass</emphasis> 设置 "
-"transaction manager factory。它的缺省值是 <literal>org.jboss.cache."
-"BatchModeTransactionManagerLookup</literal>。它告诉缓存不要参与 JTA 相关的事"
+"<emphasis role=\"bold\">TransactionManagerLookupClass</emphasis> 设置事务管理者工厂（transaction manager factory）。它的缺省值是 <literal>org.jboss.cache."
+"BatchModeTransactionManagerLookup</literal>。它告诉缓存不要参与 JTA 专有的事"
"务。作为替代，缓存管理自己的事务来支持细颗粒度的复制。"
#. Tag: para
@@ -904,10 +907,12 @@
"cluster before the web request completes. However, synchronous replication "
"is much slower."
msgstr ""
+"<emphasis role=\"bold\">CacheMode</emphasis> 控制缓存如何被复制。其有效值是 <literal>REPL_SYNC</literal> 和 "
+"<literal>REPL_ASYNC</literal>。两者都会使客户请求线程用当前的会话内容更新本地缓存，然后向群集里其他成员上的缓存发送消息，告诉它们进行相同的修改。如果使用 REPL_ASYNC（缺省），只要把更新消息放入网络，请求线程就会返回。如果使用 REPL_SYNC，在请求线程从所有群集成员获得响应消息、表示更新成功之前，它会一直阻塞。使用同步复制可以确保在请求完成前应用修改。然而，同步复制会相对较慢。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:182
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ClusterName</emphasis> specifies the name of the "
"cluster that the cache works within. The default cluster name is the the "
@@ -916,8 +921,7 @@
msgstr ""
"<emphasis role=\"bold\">ClusterName</emphasis> 指定了缓存所服务的群集的名字。"
"缺省的群集名是 \"Tomcat-\" 后面跟着当前的 JBoss 分区名。所有节点都应该使用相"
-"同的群集名。虽然会话复制能够和 JBoss 的其他群集服务共享同一通道（多点传送地址"
-"和端口），复制还是应该有自己的群集名。"
+"同的群集名。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:187
@@ -936,37 +940,35 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:192
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ClusterConfig</emphasis> configures the underlying "
"JGroups stack. Please refer to <xref linkend=\"jbosscache-jgroups\"/> for "
"more information."
msgstr ""
-"<emphasis role=\"bold\">ClusterConfig</emphasis> 包含底层 JGroups 栈（参见 "
-"<xref linkend=\"jbosscache-jgroups\"/>）的配置。"
+"<emphasis role=\"bold\">ClusterConfig</emphasis> 配置底层的 JGroups 栈（参见 "
+"<xref linkend=\"jbosscache-jgroups\"/>）。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:195
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis> sets the maximum "
"number of milliseconds to wait for a lock acquisition when trying to lock a "
"cache node. The default value is 15000."
msgstr ""
-"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis> 设置以毫秒为单位的"
-"等待所锁定捕获（lock acquisition）的最长时间。它的缺省值是 15000。"
+"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis> 设置在锁住节点时以毫秒为单位的"
+"等待获取锁（lock acquisition）的最长时间。它的缺省值是 15000。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:199
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">SyncReplTimeout</emphasis> sets the maximum number "
"of milliseconds to wait for a response from all nodes in the cluster when a "
"synchronous replication message is sent out. The default value is 20000; "
"should be a few seconds longer than LockAcquisitionTimeout."
-msgstr ""
-"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis> 设置以毫秒为单位的"
-"等待所锁定捕获（lock acquisition）的最长时间。它的缺省值是 15000。"
+msgstr "<emphasis role=\"bold\">SyncReplTimeout</emphasis> 设置当发送同步复制消息时等待所有节点的响应的最大时间。它的缺省值是 20000 毫秒。它应该比 LockAcquisitionTimeout 长几秒。"
#. Tag: title
#: Clustering_Guide_HTTP.xml:207
@@ -976,14 +978,14 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:208
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"To enable clustering of your web application you must tag it as "
"distributable in the <literal>web.xml</literal> descriptor. Here's an "
"example:"
msgstr ""
"为了启用 web 应用程序的群集，你必须在 <literal>web.xml</literal> 描述符里把它"
-"标记为 distributable。下面是一个例子："
+"标记为 distributable。下面是一个例子： "
#. Tag: programlisting
#: Clustering_Guide_HTTP.xml:210
@@ -1050,14 +1052,15 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:214
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>replication-trigger</literal> element determines what triggers "
"a session replication (i.e. when is a session is considered <literal>dirty</"
"literal> and in need of replication). It has 4 options:"
msgstr ""
"<literal>replication-trigger</literal> 元素决定用什么触发状态复制（或什么时候"
-"会话被认为是 dirty 的）。它有四个选项："
+"会话被认为是 <literal>dirty</"
+"literal> 的并需要进行复制）。它有四个选项："
#. Tag: para
#: Clustering_Guide_HTTP.xml:218
@@ -1735,3 +1738,4 @@
"properly handle the element in JBoss AS 4.2.4 and later as well was in EAP "
"4.2.0.GA_CP05 and 4.3.0.GA_CP03 and later."
msgstr ""
+
More information about the jboss-cvs-commits
mailing list